Private beta

Machines for your software factory.

Ortam runs each coding agent in a Sandbox: a Linux VM with sudo and Docker. It saves the disk while the agent works, so the next job starts with the repo, the dependencies and the images already in place.

Request access Run your first command

One Sandbox

Step 1 of 4Set up onceThe first job clones the repo, installs packages and pulls images. A sandbox deleted after each job repeats all of it every time.

What you build and what Ortam runs

Your factory

Users and sign-in
Repositories and models
Agents and the task queue
Review, tests and shipping

Ortam

A Linux VM per Sandbox
The saved disk
Every command and its output
Provider logins, renewed outside the VM

Your users never need an Ortam account. Your backend holds one organization key and assigns each Sandbox to a user, project or task.

your-factory

$ ortam lsNAME            STATE     LAST SAVE    LAST JOBagent-checkout  running   12s ago      fix flaky cart testagent-billing   running   40s ago      upgrade the Stripe SDKagent-search    stopped   yesterday    add search filtersagent-docs      stopped   2 days ago   rewrite the API docs# a new job comes in for agent-search$ ortam run agent-search -C app -- claude -p "paginate /search"Started from yesterday's save in 21s.Done in 6m 10s. 4 files changed, tests passing.

What a Sandbox does

Keeps its setupStop it tonight. Tomorrow the tests run without reinstalling.

Each save covers the whole disk, including system packages, Docker images and volumes, and your code makes no checkpoint calls. Running processes aren’t saved; enabled services come back when the Sandbox starts. How saves work

Keeps running when you disconnectYour orchestrator can restart mid-test. The tests keep running.

Reattach to a running command and read its output from where you left off. Ortam never reruns a command for you, and if it can’t tell how one ended, it says so. How commands run

Branches from a SnapshotStart three fixes from the same known‑good Sandbox.

Take a Snapshot once a Sandbox is set up the way you want, then start as many new ones from it as you need. Each copy writes to its own disk and keeps working after you delete the original. How Snapshots work

Keeps long-lived logins off the VMAgents use your Claude or ChatGPT plan without holding the account login.

Sign in and choose which Sandboxes may use the account. Ortam keeps and renews the login outside the VM, gives agents short-lived credentials that are never saved (API-key accounts get the key), and says when the holder must sign in again. A copy an agent writes to disk is saved like any other file. How Connections work

Comes back after a hardware failureA host failure can lose the work since the last save.

If its hardware fails, the next start or command brings the Sandbox back on new hardware from its last save. Ortam tells you how old that save is and which commands were running, so you decide what to rerun. What a host failure can lose

Runs in its own VMA whole VM per Sandbox, not a container on a shared kernel.

Each Sandbox gets Ubuntu 24.04 on its own VM, from 2 vCPUs and 4 GB of memory up to 8 vCPUs and 16 GB. systemd manages services as on any Linux server, and Node.js, Python, git, Claude Code and Codex CLI come preinstalled. Sandboxes run in Germany and Finland. What runs in a Sandbox

Run your first command

Install the CLI, log in with your organization key, then create a Sandbox and run commands in it.

curl -fsSL https://ortam.dev/install.sh | sh

ortam login
ortam create my-sandbox
ortam run my-sandbox -- git clone https://github.com/you/app
ortam run my-sandbox -C app -- npm ci
ortam run my-sandbox -C app -- npm test
ortam attach my-sandbox
ortam stop my-sandbox
ortam snapshot my-sandbox

import { Ortam } from "@ortam/sdk";

const ortam = new Ortam(); // reads ORTAM_API_KEY
const repo = "https://github.com/you/app";

const sandbox = await ortam.sandboxes.create({ name: "my-sandbox" });
await sandbox.run(["git", "clone", repo]).result();
await sandbox.run(["npm", "ci"], { cwd: "app" }).result();

const run = sandbox.run(["npm", "test"], { cwd: "app" });

for await (const line of run.output()) console.log(line);

// An exit code, or another outcome such as a timeout
const result = await run.result();

curl https://api.ortam.dev/v1/sandboxes/$SANDBOX_ID/executions \
  -H "Authorization: Bearer $ORTAM_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"argv": ["npm", "test"], "cwd": "/home/developer/app"}'

Read the docs

Billed by the second while it runs

The plan is $20 a month, and all of it counts toward usage. A running Sandbox is billed by the second; a stopped one pays only for its disk, at 1¢ per GB‑month.

Small2 vCPUs · 4 GB memory · 40 GB disk$0.018/hrcapped at $13/mo
Medium4 vCPUs · 8 GB memory · 80 GB disk$0.036/hrcapped at $26/mo
Large8 vCPUs · 16 GB memory · 160 GB disk$0.072/hrcapped at $52/mo

Sandboxes running a day

Per month, before saved disks$2.16 per Sandbox

Billing starts when the VM is ready, so failed boots and waits for hardware are free. Saved disks are kept while your plan is active. Prices are planned for launch and may change before it. Sizes, billing and limits

Questions

What does it cost?

$20 a month, and all of it counts toward usage. A running Sandbox is billed by the second, from $0.018 an hour for Small, never more than its size’s monthly cap; a stopped one pays only for its saved disk, at 1¢ per GB‑month. Prices are planned for launch. Pricing and limits

Can I use it now?

It’s in private beta, and we’re letting teams in a few at a time. Email access@ortam.dev with what your agents run and roughly how many Sandboxes you need.

How is it different from E2B or Vercel Sandbox?

Most agent sandboxes now keep something between runs. Ortam saves a Sandbox’s whole disk on a schedule while the agent works, not only when it stops, keeps saved disks for as long as your plan is active, and runs each Sandbox in its own VM. What each provider keeps, compared

Where does it run?

In Germany and Finland. A Sandbox’s saved data stays in the location where it was stored.

Can agents run Docker?

Yes. The developer user has sudo in the Sandbox’s VM and can run Docker, and every save keeps Docker images and volumes with the rest of the disk.

Is the saved disk encrypted?

Yes. Each save is encrypted with its own key before it leaves the machine, and those keys never enter the VM.

Can I read files without starting the VM?

Yes. Reads and exports of a stopped Sandbox come from its saved disk and don’t boot anything, so they use no compute.

Can I change a Sandbox’s size?

Yes, while it’s stopped, if its disk fits the new size. The next start uses the new size and the same disk.

Request access

We’re letting teams in a few at a time. Tell us what your agents run and roughly how many Sandboxes you need, and we’ll send an organization key.

Email access@ortam.dev