Coding agents for your customers
Updated 27 October 2026
Agencies, agent products and app builders give each customer’s coding agent a machine it keeps. On Ortam, that machine is a Sandbox per customer, project or user. Your customers never sign in to Ortam. Your product calls the API with your organization key and decides which Sandbox serves whom.
How do you give each customer a machine?
Create a Sandbox for each customer, project or user. It keeps their repository, installed packages and Docker images between visits.
To start every customer from a template, set up one Sandbox the way new customers should find it, with your framework, tools and starter files. Take a Snapshot of it, a saved copy of its files that never changes. Create each customer’s Sandbox from that Snapshot. Each copy writes to its own disk and keeps working after you replace the template.
How do you keep customers apart?
Each Sandbox runs in its own VM, so one customer’s agent never shares a kernel or a disk with another’s. The agent has sudo inside its VM. It can’t change the kernel, boot, network or storage, or read Ortam’s credentials.
A grant lets one Sandbox use one AI account. A new Sandbox has no grants. An organization key can reach every Sandbox in its organization. Customers who must also be kept apart by keys, accounts and grants get an organization each.
Can customers use their own Claude or ChatGPT account?
Yes. Your product can set up a Connection that belongs to one of your customers. The customer signs in to their Claude or ChatGPT account through the provider’s own sign-in. Ortam keeps and renews the login outside every Sandbox. Your product grants it only to that customer’s Sandboxes. When the provider signs the account out, the Connection’s status says so. Commands that need it then fail before they start, until the customer signs in again.
How do customers get into their machine?
- Through your product. Your product sends the agent’s commands to the customer’s Sandbox and reads each command’s state and result. Ortam stores each command’s output with positions. If your product disconnects while reading, it can reconnect and continue where it left off.
- Through a terminal. Give a customer’s developer a private link that names one Sandbox and expires. Opening it starts a stopped Sandbox. The developer needs no Ortam account.
What does an idle customer cost?
Only their saved disk, once their Sandbox is stopped. Stop it when they leave. A stopped Sandbox has no VM. Its saved disk costs $0.01 per GB a month. The next command or terminal starts it from its last completed save. Ortam bills your organization, and what you charge your customers is up to you. Prices are planned for launch. Pricing and limits lists the sizes.
Common questions
What happens to a customer’s work if hardware fails?
The Sandbox comes back on new hardware from its last completed save when it’s next started. Work since that save can be lost. Ortam reports how old the save is and which commands were running. Host failures explains how to limit that loss.
Can a customer’s files be shown in my product while their Sandbox is stopped?
Yes. Ortam reads a stopped Sandbox’s files from its saved disk without starting it. Showing a file tree or offering a download uses no compute. Each read says which save it comes from.