Roadmap
Built in stages, with the limits visible.
Start with a qualified local update workflow. Add connected hosts and private previews, then broaden the operations and runtimes that can be supported.
This is the implementation sequence, not a release-date commitment.
- Development
Core qualification
Complete registry authentication, interrupted-operation recovery, release checks, and repeatable runtime qualification.
- Remediate private-registry authentication used by the container engine.
- Complete recovery when an update is interrupted.
- Establish repeatable release checks and publish qualified Docker runtime combinations.
- Prepare the public Core release and integrate its selected Apache-2.0 license.
Current work manages existing watched containers. Production qualification and the public licensed release are still ahead.
- Planned
Connected Cloud
Add identity, node enrollment, read-only visibility, and private application previews.
- Connect designated customer hosts through outbound node connections.
- Add project identity, host observations, and scoped reviewer access.
- Accept eligible revisions and verified immutable artifacts from trusted CI.
- Provision approved preview templates with synthetic data, resource limits, expiry, and tracked cleanup.
The first native-preview model excludes untrusted sources. Customer applications run on designated customer infrastructure.
- Planned
Agent operations and releases
Add scoped MCP actions and separately approved release workflows after their execution and recovery boundaries are qualified.
- Give the dashboard, API, CLI, and MCP interface the same permission and operation model.
- Scope requests to named projects, environments, and actions.
- Keep production approval separate from preview creation and review.
- Re-evaluate release plans when their artifacts or target state change.
Agent access does not grant a root shell. A successful preview does not authorize a release, and its cleanup does not depend on one.
- Later
Broader compatibility
Qualify Podman and selected external execution providers against real customer needs.
- Qualify rootful Podman before a separate rootless Podman track.
- Evaluate user-selected external execution services for stronger isolation.
- Publish support boundaries only after implementation and repeatable qualification.
No additional runtime or external sandbox provider is currently advertised as a working, qualified integration.
How progress is described
Evidence before an availability claim.
The status inventory was reviewed on against development documentation and product decisions. Development means that code exists at that checkpoint. It does not mean production qualification is complete.
Cloud access, a public Apache-2.0 Core release, and qualified Podman support remain ahead. The project will publish support boundaries as the relevant implementation and checks are completed.
Read the complete status inventoryThe first pilot
Help shape the first preview workflow.
We are looking for developers and small teams already running containerized applications on their own servers. Join the waitlist to hear when the initial pilot and closed beta are ready.
Join the preview waitlist