Internet access with an enforced boundary

New or rebuilt managed ⁠Docker workspaces restrict public HTTP/HTTPS access to approved hosts while keeping required agent endpoints available. Supported hosts require Rootful ⁠Docker 28+ or verified Rootless ⁠Docker 29.9.1+. Legacy containers migrate only on explicit rebuild.

How it works

  1. Choose approved destinations

    Choose access packages at shared system, user, project-group and repository scopes. Team administrators approve shared templates and control additional destinations. Explicit repository policies stay unchanged until you choose inheritance.

  2. Enforce outside the agent

    Supported managed containers route public HTTP/HTTPS access through the workspace boundary. A prompt instruction alone does not change the network allowlist.

  3. Keep approved sites for the repository

    An agent can request public hostnames through a typed repository-access request. Approve selected hosts once and retain them for future sessions. Team ceilings still apply; saved settings, queued reloads and verified gateway access have separate states.

  4. Keep Web fonts optional

    Add the Web fonts package to a private Internet-policy template or scoped defaults. It allows Google Fonts stylesheets and font files; saving policy and verified gateway application remain separate.

  5. Start from a curated template

    The default template covers package registries, toolchain installers, container registries, browser test downloads, documentation, certificate revocation and many database hosts, each as a separate editable group.

  6. Opt in to user-content hosts

    Shared object storage and user-content hosts ship as unchecked opt-in groups: Google Cloud Storage, ⁠GitHub Actions blob downloads, Hugging Face, cloud container registries, JitPack, Read the Docs and Stack Overflow. Any account can upload and read content there, so a compromised dependency could use them for command-and-control or data exfiltration. Enable them only for projects that need them.

  7. Migrate deliberately

    Legacy containers and network-mode changes require explicit recreation. Destination changes in an enforced container use a queued gateway reload; only a matching host acknowledgement confirms application. Supported ⁠Docker prerequisites must pass before a new restricted session starts.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

SettingsREAL UI

Loading the recorded terminal…

Walkthrough paused

Release videos

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.