SOLO · ONE LAPTOP Everything on one laptop For trying devctrl or working solo, with no server to set up.
A terminal or browser on your laptop talks to Core over localhost, and Core starts agent containers in the laptop’s local Docker. YOUR LAPTOP Terminal or browser TUI Web console Core Controller and web gateway Local Docker Claude Code Codex localhost Docker API A terminal or browser on your laptop talks to Core over localhost, and Core starts agent containers in the laptop’s local Docker. YOUR LAPTOP Terminal or browser TUI Web console Core Controller and web gateway Local Docker Claude Code Codex localhost Docker API The installer uses Local Docker mode when it runs without arguments. SSH and a remote server are not required; --docker-context selects another Docker context. devctrl local tui and devctrl local web open the terminal and browser consoles.SOLO · ONE SERVER One server for all your sessions For one developer who wants agents to keep working while the laptop is closed.
A terminal reaches Core on your server over SSH, a browser or the desktop app over an encrypted WebSocket, and Android or Telegram over HTTPS; Core runs the agent containers, optionally with an NVIDIA GPU, on the same server. YOUR SERVER Terminal Browser or desktop app Android or Telegram Core Controller and web gateway Agent containers Claude Code Codex Optional NVIDIA GPU SSH Encrypted WebSocket HTTPS Host agent A terminal reaches Core on your server over SSH, a browser or the desktop app over an encrypted WebSocket, and Android or Telegram over HTTPS; Core runs the agent containers, optionally with an NVIDIA GPU, on the same server. YOUR SERVER Terminal Browser or desktop app Android or Telegram Core Controller and web gateway Agent containers Claude Code Codex Optional NVIDIA GPU SSH Encrypted WebSocket HTTPS Host agent devctrl tui remote shows the server-hosted console over SSH; devctrl web remote opens its private HTTPS link.Turn on NVIDIA GPU passthrough per Project, or run one GPU service such as Ollama and grant it to selected Projects. The Hosts screen shows every GPU. CLOUD · HOME NETWORK A home server with no public IP For a machine behind a home router, reached from a phone or laptop on any network.
A phone or laptop on any network opens RANDOM-ID.on.devctrl.dev; the devctrl edge passes the still-encrypted connection to the home server through the tunnel its connector opened, so the router needs no open port or public address. HOME NETWORK Phone or laptop Any network devctrl edge RANDOM-ID.on.devctrl.dev Home server Core and web console Bundled connector HTTPS, TLS ends on your server Encrypted tunnel A phone or laptop on any network opens RANDOM-ID.on.devctrl.dev; the devctrl edge passes the still-encrypted connection to the home server through the tunnel its connector opened, so the router needs no open port or public address. HOME NETWORK Phone or laptop Any network devctrl edge RANDOM-ID.on.devctrl.dev Home server Core and web console Bundled connector HTTPS, TLS ends on your server Encrypted tunnel devctl cloud link lists the server in devctrl Cloud and gives its console a stable address, RANDOM-ID.on.devctrl.dev, with no own domain, quick tunnel or open port.devctl cloud connect prints the link for the desktop and mobile apps and the terminal command for that address.CLOUD · SEVERAL SERVERS Several servers, one devctrl Cloud account For one person with a home server, an office server and a GPU box.
You sign in to app.devctrl.dev with GitHub, GitLab or Google and see all your linked servers; each server keeps an encrypted outbound tunnel to the devctrl edge, and your laptop or phone opens each console at its own on.devctrl.dev address. Laptop or phone app.devctrl.dev Sign in with GitHub, GitLab or Google All your servers devctrl edge RANDOM-ID.on.devctrl.dev Home server Office server GPU box NVIDIA GPU Sign in once HTTPS Encrypted tunnel You sign in to app.devctrl.dev with GitHub, GitLab or Google and see all your linked servers; each server keeps an encrypted outbound tunnel to the devctrl edge, and your laptop or phone opens each console at its own on.devctrl.dev address. Laptop or phone app.devctrl.dev Sign in with GitHub, GitLab or Google All your servers devctrl edge RANDOM-ID.on.devctrl.dev Home server Office server GPU box NVIDIA GPU Sign in once HTTPS Encrypted tunnel Run devctl cloud link on each server and approve its device code in the browser; each server gets its own random address. devctl cloud login signs your computer in, devctl cloud servers lists every server and devctl cloud open opens its console.CLOUD · TEAM ORGANIZATION A team organization on devctrl Cloud For a team that signs in to its servers with one account per person.
Teammates invited by email sign in to the organization on app.devctrl.dev, open a server’s console through the devctrl edge, and sign in to its Core with their devctrl Cloud account. Teammates Invited by email app.devctrl.dev Organization, members and roles Sign in with GitHub, GitLab or Google devctrl edge Server A Sign in with devctrl Cloud Server B Sign in with devctrl Cloud Sign in HTTPS OpenID Connect Encrypted tunnel Teammates invited by email sign in to the organization on app.devctrl.dev, open a server’s console through the devctrl edge, and sign in to its Core with their devctrl Cloud account. Teammates Invited by email app.devctrl.dev Organization, members and roles Sign in with GitHub, GitLab or Google devctrl edge Server A Sign in with devctrl Cloud Server B Sign in with devctrl Cloud Sign in HTTPS OpenID Connect Encrypted tunnel Invite people to the organization by email and give them a role on each server they use. With Sign in with devctrl Cloud turned on, members sign in to a linked Core with their devctrl Cloud account; the Core maps each account to its own server user. Removing someone from the organization removes their server memberships, so devctrl Cloud no longer lists those servers for them or signs them in to them. CLOUD · CONTRACTORS Contractors see only their servers For giving a contractor or client access to some of your servers, not all of them.
A contractor signs in to app.devctrl.dev, sees only Server A, opens it through the devctrl edge and signs in to it with devctrl Cloud; Server B stays hidden from them. Contractor app.devctrl.dev Member of Server A only devctrl edge Server A Sign-in allowed Server B Not visible to the contractor Sign in HTTPS Sign in with devctrl Cloud A contractor signs in to app.devctrl.dev, sees only Server A, opens it through the devctrl edge and signs in to it with devctrl Cloud; Server B stays hidden from them. Contractor app.devctrl.dev Member of Server A only devctrl edge Server A Sign-in allowed Server B Not visible to the contractor Sign in HTTPS Sign in with devctrl Cloud Invite them to the organization and add them only to the servers they work on; an organization member without a server role sees no servers. Allow devctrl Cloud sign-in for them on those servers; what they may do inside is set by the Core. APPLE PLATFORMS · MAC + SERVER Agents on the server, Xcode on your Mac For iOS and macOS developers whose builds and simulators need a Mac.
Agents edit the repository in a container on the server; Local copy brings the checkout to a folder on your Mac that Xcode builds; devctl forward brings the backend port to the Mac’s localhost for the simulator; Exchange folders sync screenshots and logs both ways. YOUR MAC SERVER Xcode and the simulator Builds the local copy Local copy of the repository Exchange folder Backend and dev servers Agents edit the repository Claude Code Codex Exchange folder Port forward to localhost Local copy, every 30 s Screenshots and logs Agents edit the repository in a container on the server; Local copy brings the checkout to a folder on your Mac that Xcode builds; devctl forward brings the backend port to the Mac’s localhost for the simulator; Exchange folders sync screenshots and logs both ways. YOUR MAC SERVER Xcode and the simulator Builds the local copy Local copy of the repository Exchange folder Backend and dev servers Agents edit the repository Claude Code Codex Exchange folder Port forward to localhost Local copy, every 30 s Screenshots and logs Local copy keeps a folder on the Mac in step with the server checkout, uncommitted changes included, about every 30 seconds. Open it in Xcode and build.devctl forward add brings a Project port to the Mac’s localhost, so the app in the simulator can reach the backend the agent runs.MIXED · TWO HOSTS Your Mac joins the server as a Host For keeping quick sessions on the Mac and sending heavy work to the server.
One Core on the server drives two Hosts: local Docker on your Mac for light Projects and the server for heavy ones; the Mac Host connects outward to Core. YOUR MAC SERVER Console Mac Host Light Projects Core One console for both Hosts Server Host Heavy Projects Claude Code Codex SSH · HTTPS Outbound Host link Host agent One Core on the server drives two Hosts: local Docker on your Mac for light Projects and the server for heavy ones; the Mac Host connects outward to Core. YOUR MAC SERVER Console Mac Host Light Projects Core One console for both Hosts Server Host Heavy Projects Claude Code Codex SSH · HTTPS Outbound Host link Host agent devctrl host install local (over SSH) or devctrl connect URL --local-docker (over HTTPS) enrolls the Mac’s Docker as another Host.Place each Project on the Mac or on the server. devctl project deploy moves it later, after a confirmed stop. TEAM · SHARED SERVER One server for a whole team For several developers sharing compute without sharing environments.
Several developers sign in to one Core on the team server; each gets private agent containers under a per-user budget, and the containers clone from and push to shared GitHub or GitLab repositories. TEAM SERVER Developer A Developer B Developer C Core User accounts and policy Private containers One set per developer Per-user budget Shared repositories Own sign-in Host agent Clone and push Several developers sign in to one Core on the team server; each gets private agent containers under a per-user budget, and the containers clone from and push to shared GitHub or GitLab repositories. TEAM SERVER Developer A Developer B Developer C Core User accounts and policy Private containers One set per developer Per-user budget Shared repositories Own sign-in Host agent Clone and push Install with --users: each developer gets their own projects, accounts, secrets, containers and storage. Set CPU, memory and storage budgets per user. Usage by user shows tokens, estimated cost and disk per person. ELASTIC · CLOUD + SANDBOXES Burst to cloud machines and sandboxes For running many temporary tasks in parallel without buying hardware.
Core on your server calls cloud provider APIs to create VMs that join as Hosts and to open disposable sandbox workspaces; Overnight can power a cloud server off when the work is done. YOUR SERVER Core Persistent Projects Cloud VMs created on demand Docker and Host agent Claude Code Disposable sandbox workspaces Separate checkout Provider API: create, power off Sandbox API Core on your server calls cloud provider APIs to create VMs that join as Hosts and to open disposable sandbox workspaces; Overnight can power a cloud server off when the work is done. YOUR SERVER Core Persistent Projects Cloud VMs created on demand Docker and Host agent Claude Code Disposable sandbox workspaces Separate checkout Provider API: create, power off Sandbox API Cloud adapters create a VM at Hetzner, DigitalOcean, Vultr, Linode, Hostman or Proton, install Docker and register it as a Host. Overnight archives the work to your S3 storage and powers the cloud server off once every session has finished or needs you. TWO CORES · FEDERATION A personal Core linked to the company’s For keeping your own installation separate while its agents work with a team’s.
A personal Core and a company Core, each with its own hosts, accounts and secrets, exchange session lists and Project messages for one linked Project over signed HTTPS. Personal Core Your hosts, accounts and secrets Claude Code Company Core The team’s hosts, accounts and secrets Codex Signed HTTPS: sessions and messages A personal Core and a company Core, each with its own hosts, accounts and secrets, exchange session lists and Project messages for one linked Project over signed HTTPS. Personal Core Your hosts, accounts and secrets Claude Code Company Core The team’s hosts, accounts and secrets Codex Signed HTTPS: sessions and messages Agents message a session on the other Core as @handle@coreId; messages wait in a queue while the peer is offline. Files, terminals, credentials, hosts and budgets are never shared.
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.