Enterprise on your own server

With Enterprise on-premise, your code is stored and built on your own servers, and your engineers work in the same dashboard at my.detachbox.com as on every plan. Each engineer's terminals run on their own node, on a server or VM of yours in your data center or your cloud account: agents, Docker, builds, projects and home folders all live there. We keep the node's software and the terminal image current.

What runs on your server

• Every terminal: a fresh Linux container with Docker, sudo, Claude Code, Codex and OpenCode, the same as on our servers.
• Your account disk: projects and their home folders, on a ZFS pool on a disk of your server.
• Builds, package caches, Docker images and containers.
• detachbox-node-host, the one program of ours on the server, and the node's Cloudflare Tunnel. Both only dial out, so you open no inbound port.

What stays with detachbox

The dashboard, sign-in, Vault, and the refresh tokens of your Claude and ChatGPT subscriptions, encrypted on our server. A terminal gets an access token and nothing that can mint a new one. Agents call their model provider straight from the terminal, so what an agent sends its model goes to that provider, as on every plan.

The node's software and the terminal image are ours to keep current. Ubuntu, its kernel and the hardware are yours to look after.

One server, one account

A node serves one detachbox account, and that account's Compute takes the whole server:

Your contract sets how many terminals run at once, the network speed of each and the largest file you can drop into a terminal. For a team on Enterprise on-premise, each engineer's account gets its own node, on its own server or VM.

The account a node goes to has no Compute yet: a Compute never moves between nodes.

What the owner sees in the dashboard

• The Compute page reads Your own node, billed under your contract where other plans show a price. There is no plan to change and nothing to pay in the dashboard; size and billing go by your contract.
• Until the node is live, the Compute and Terminals pages read Your own node is on its way in place of the plans, with where it stands: waiting for the install command, installing, or stopped (then with Write to support).
• The install sets up your Compute by itself. If you delete it, the Compute page offers Set up Compute on the same node, with no plan to pick and nothing to pay.
• When the node has not answered for a minute, the top bar and the Compute page read Node offline since 14:02, and an open terminal says it reconnects by itself once the node is back. Your files stay on the server. After 10 minutes of silence the account's owner gets an email, and one more when the node answers again.
• Activity records when your node was set up, when your contract changed its size and when the node left the account.

Get a node

1. Tell us about your team through the form on Enterprise. We agree the terms and the SLA.
2. detachbox issues an enrollment token for your account. It works for one server and one install. A server has 7 days to enroll with it, and after enrolling the token takes reruns of that install for 7 more days. A new token replaces it.
3. Your admin checks the server against what it needs and runs the install command. When the server enrolls, the account's owner gets an email with its host name, address, key fingerprint and time; if that server is not yours, write to support at once. 30 to 60 minutes later, your account's terminals run on your server.