Your team's agents, on a node of your own
Every engineer gets an always-on box with Docker and their agent ready. Enterprise puts those boxes on a dedicated node, under an SLA, paid by invoice. Tell us your team's size and builds, and we set it up around you.
Dedicated node · SLA · Paid by invoice
A node your company runs on alone
Hardware nobody else touches
Your boxes alone on the node: its CPU, memory and disk go to your engineers and their agents, and its kernel runs nobody else's code.
Uptime your team plans the night around
Your SLA sets the uptime and response times your overnight agents run on.
One invoice, your terms
Pay by invoice instead of a card per box, made out to your company with its tax details.
Sized to the team
As many boxes as the team needs, in the sizes it needs, set up with you before the first engineer signs in.
Business for a few boxes, Enterprise for the fleet
Both Business plans run on the shared node and bill per box. Enterprise moves the fleet to a node of its own.
| Business | Business Plus | Enterprise | |
|---|---|---|---|
| Price | $149 a month per box | $299 a month per box | Set with you |
| Box | 8 vCPU · 16 GB · 300 GB | 16 vCPU · 32 GB · 600 GB | Sized to the team |
| Snapshots | Daily, kept 7 days · 20 checkpoints | Daily, kept 30 days · 50 checkpoints | Set with you |
| Support | Priority, reply within 4 hours | Priority, reply within 4 hours | Under the SLA |
| Billing | Card, invoices to your company with VAT or tax ID | Card, invoices to your company with VAT or tax ID | Invoice |
| Hardware | Shared node in Kazakhstan | Shared node in Kazakhstan | A node of your own |
What your security team will ask
Short answers here, the full model on the security page.
Subscription tokens stay on our server
Codex and Claude refresh tokens are encrypted on the server. A box holds only a short-lived access token, renewed on schedule.
Company keys never enter a box
With Vault, each box gets its own Sallyport Cloud identity with no access until you grant it, service by service.
Every sign-in hardened
Passkeys, authenticator codes and Google sign-in, a list of signed-in devices, and a log of every start, stop, reset and size change.
Boxes walled off
Unprivileged containers with their own user ranges, no route to private networks or to each other, outbound mail blocked.
- Read the security model
Your team on its own node in three steps
- Form
Tell us your team's size and builds
How many engineers, which agents, how heavy the builds, what your security team needs to see.
- Call
Settle the node and the terms
Box sizes, the SLA and how you pay, in one conversation and one document.
- Boxes
Engineers sign in
Each person starts their boxes and connects their own subscriptions. The agent waits in the first tab.
Talk to us about Enterprise
Team size, agents, what has to run overnight. We answer by email.
Questions about this
What changes with a dedicated node?
Your boxes run alone on the hardware. Everything else stays as your engineers know it: the dashboard, the terminal, previews, Vault and the agents.
Do engineers keep their own subscriptions?
Yes. Each engineer connects their own Codex and Claude subscriptions, sees their limits and can turn on rotation across them.
Can we start on Business?
Yes. Business and Business Plus start from the dashboard today, with snapshots, priority support and company invoices from the first day.
Where do the boxes run?
In Kazakhstan, on our own hardware. Teams in Central Asia get the lowest ping, and the agents call Anthropic and OpenAI straight from the box.