Sandboxes or Computers?
Most work starts in a Sandbox. Reach for a Computer when someone has to see and use a real screen. When the result should stay online for your users, publish it with App Engine.
A fast, isolated machine for code. Run commands, edit files, install packages, open a live preview URL, and drive the built-in browser. Pauses when idle and wakes on the next request.
A durable cloud desktop. A real Linux screen with a browser, desktop apps, mouse and keyboard control, a live view a person can take over, and state that stays between sessions.
Ready to go live? App Engine keeps what you built online at a stable URL, with your own domain, versions and rollback.
Pick by what you need
| You want to | Use |
|---|---|
| Run code, build, test, or install packages | Sandbox |
| Show a live preview of an app while you build it | Sandbox |
| Let an agent browse and fill forms in a browser | Sandbox, with its built-in browser |
| Use desktop apps, or anything that needs a full screen | Computer |
| Keep logins, files and a desktop around for days | Computer |
| Let a person watch and take over an agent’s screen | Either: the sandbox browser or the computer desktop both have a live view |
| Keep an app online for your users | App Engine |
Create one
Often you use both
A typical agent product writes and runs code in a Sandbox, uses a Computer when a task needs a real desktop, and publishes the finished app with App Engine. See Agent device selection for the full decision guide, including when an agent needs no machine at all.
Next steps
- Quickstart: create your first sandbox in minutes.
- Computers: lifecycle, streaming and embedding.
- Build an app like…: pick a product and get a step-by-step guide.