Computer

Cloud computers for agents Where real work gets done at the lowest cost, at any scale.

Start for free

Build on the frontier with Computer for agents that think, work and evolve.

Run code and commands

Read and write files, run scripts and build software in a full shell. Output streams back as each command runs.

Learn about running commands⁠

An example terminal. An agent clones a billing service, finds why a test fails, fixes it and pushes the commit. Then you can type commands into it yourself.

billing · bashcmp-7hx2

A desktop you can share

Open apps, take screenshots, click and type. Share a link so a person can watch live or use the mouse and keyboard.

Learn about the desktop⁠

An example desktop. An agent's pointer creates an invoice in a browser, then opens Text Editor from the Dock, ticks off a task and closes it. Take control to use the desktop yourself, then release it.

Files
Browser
Text Editor
Terminal

Bridge your application and the agent’s environment

Write functions in your application or agent harness, and the agent runs them as shell commands. Each call is handled securely in your own code, outside the computer, so your keys never enter it.

Learn about extensions⁠

An interactive example of a shell command calling an application function outside the computer. Run a command, then hover or select a code line to explore it.

order
In the computer
Shipped. Arriving Friday.
In your application

“Shipped. Arriving Friday.”

The function’s return value appears as output in the shell.

Hover to explore. Click to keep a line selected.

Create computers from your own templates

Install the tools, add the project files and configure a template once. Every computer created from it starts with that setup.

Learn about templates⁠

An example template named billing, drawn as a stack with one layer per build step, each stickered with the logos of what it adds: an Ubuntu image, packages such as Chrome, Spotify or Git, tools such as Bun, uv or Python, and a GitHub repository. Each visit picks a few of each. The whole stack is the template. Point at a layer to lift the ones above it.

Fork a computer

Create a computer from another’s state. Control exactly what the new computer carries over.

Learn about forks⁠

A computer drawn as a stack with its state as stickers on top, and the computers forked from it drawn as a tree. Each fork starts with every sticker its source has at that moment and adds one of its own, while the source carries on. Click a computer to fork it.

Resources adjust automatically to each task so there’s nothing to provision or tune.

Pay only for what the computer uses

A computer freezes while it is idle and only storage is used. When work arrives, it resumes in under 10ms with its processes and files as they were, so there is nothing to snapshot or restore.

Learn about computers⁠

Ten minutes of a computer's work, printed as dots a minute at a time: CPU above a line and memory below it. Dots appear only while it runs a command; between commands it is frozen and uses neither. Over the ten minutes it runs for one minute and is frozen for nine.

Keep secrets outside the computer

Upload secrets and the computer will hold placeholders. The proxy replaces them with the real values only in HTTPS requests to domains you allow.

Learn about secrets⁠

A computer holds OPENROUTER_API_KEY as a placeholder in the real key's format. The proxy is the computer's floor: a request to openrouter.ai, which the secret allows, leaves with the real key, and a request to evil.com leaves with the placeholder. Both keys are made up.

Control network access

Set network policies for the connections a computer can receive and make. Allow or block traffic using rules for domains, IP ranges, protocols and ports.

Learn about networking⁠

A computer sends packets to four hosts through a network policy that blocks everything except its rules. Rules allow openrouter.ai and github.com, so their packets get through; packets to evil.com and malware.io stop at the policy. Each host's rule can be added or removed.

Set usage limits

Set limits for CPU, memory, storage and exports over a period you choose. Decide whether Elios notifies you or pauses the computer if a limit is exceeded.

Learn about usage limits⁠

Four weeks of the CPU a computer used in the last 7 days, against a 100 vCPU-hour limit. A busy week pushes it past the limit, which pauses the computer until older usage leaves the window, so its usage holds near the limit. The limit can be moved, and set to notify instead of pause.

If exceeded

How much will it cost? Pay for the work, not the waiting.

Hours of work a day Every day for 30 days.
Computers Each with 2 vCPUs, 4 GiB of memory and a 40 GiB disk.

Per month

$4.19

Daytona $52.40
E2B $49.68
Vercel Sandbox $36.32
Agent37 $5.27
Elios Computer $4.19

Breakdown

Active CPU 60 vCPU-hours × $0.012$0.72
Memory 192 GiB-hours × $0.006$1.15
Storage
Template 30 GiB × $0.04$1.20
From the template 30 GiB × $0.024$0.72
Its own 10 GiB × $0.04$0.40
Total$4.19

Each disk takes 30 GiB from a template. Elios freezes each computer for 60% of the hours of work, and while it is awake bills the 25% of its vCPUs and 40% of its memory it uses. The other providers run it for every hour of work and bill its full memory throughout, and all except Vercel bill every vCPU as well. Before plan fees, network and taxes.

Edit assumptions⁠

Try Computer for free.

Start for free