Depot Sandboxes vs Railway Sandboxes
Choose Depot Sandboxes for teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool; choose Railway Sandboxes for coding agents and test runs that need to reach your Railway databases and services over the private network. Depot Sandboxes uses MicroVM on bare metal isolation; Railway Sandboxes uses Linux VM isolation.
Key differences between Depot Sandboxes and Railway Sandboxes
- Isolation: Depot Sandboxes uses MicroVM on bare metal; Railway Sandboxes uses Linux VM.
- Session length: 2 h default timeout (Depot Sandboxes) versus No cap (idle 30 min default) (Railway Sandboxes).
- SDKs and interfaces: Only Railway Sandboxes lists GraphQL API.
What they have in common
- Both are hosted platforms.
- Neither is open source.
- Both support snapshots.
- Both list TypeScript and CLI.
Depot Sandboxes vs Railway Sandboxes at a glance
| Attribute | Depot Sandboxes | Railway Sandboxes |
|---|---|---|
| What it is | MicroVM sandboxes on the bare-metal compute behind Depot CI, with a TypeScript SDK, Tailscale networking and a Managed Agents service that hosts Claude Code, Codex, Devin and Amp sessions. | On-demand Linux VMs inside a Railway environment with forks, checkpoints, Docker, private networking to your services and per-second billing; generally available since September 2026. |
| Type | Hosted platform | Hosted platform |
| Isolation | MicroVM per sandbox on bare-metal hosts ("Real microVMs, not containers") with a full Linux syscall interface, Docker and nested VMs; hypervisor not named | Isolated Linux virtual machine per sandbox; hypervisor not named |
| Open source | No | No |
| Self-host / BYOC | Not documented / Yes | Not documented / Not documented |
| SDKs | JavaScript/TypeScript, CLI | JavaScript/TypeScript, CLI, GraphQL API |
| Cold start (vendor claim) | Blog: "fast boot from a pre-cached base image"; no figure | Product page: "ready in seconds"; no figure |
| Max session | Runs until stopped or the configured timeout expires; the SDK launch post gives a default timeout of two hours with extensions; no maximum stated; a stopped sandbox cannot be restarted | No maximum lifetime stated; idle timeout destroys the sandbox after 30 minutes by default on Hobby and Pro (1-120 minutes, or disabled) and after 5 minutes on Free and Trial (1-5 minutes, cannot be disabled) |
| Persistence | Snapshots save the home and /workspace directories (not processes or memory) and seed new sandboxes; Managed Agents snapshot the workspace automatically between runs, excluding node_modules, .venv and target; stopped sandboxes cannot be resumed; persistent disk was listed as planned | Sandboxes are ephemeral; checkpoints are named server-side disk snapshots that outlive the sandbox and boot where captured; forks copy a running sandbox's disk (not memory or processes); templates cache build steps; pause/resume is not documented |
| Snapshots / pause | Yes / No | Yes / Not documented |
| GPU | Not mentioned | Not mentioned in the sandbox docs |
| Networking | Sandboxes can join your organisation's Tailscale tailnet to reach private services; Depot Cache credentials are injected by default; run secrets are scoped to up to 16 hosts each; no egress allow-list documented | Outbound internet via NAT on all sandboxes; ISOLATED (default) has no access to environment services, PRIVATE joins the environment's private network to reach databases by hostname; up to 10 public HTTPS domains per sandbox set at creation; SSH and port forwarding with an account SSH key; no egress allow-list documented |
| Pricing | Developer $20/month with 2,000 included minutes, Startup $200/month with 20,000, Business custom (dedicated infrastructure, deployment in your own AWS account); minutes are shared across Depot CI, Sandboxes and Managed Agents and measured at 2 vCPU, so the default 4 vCPU sandbox uses 2 minutes per minute; overage $0.00005 per vCPU-second, billed per second with no minimum; storage 25 GB / 250 GB included then $0.20/GB-month | Per second at Railway VM rates: $0.00001929 per GB-second of memory in use (about $50/GB-month), $0.00001929 per vCPU-second of active CPU (about $50/vCPU-month), egress $0.05/GB; idle sandboxes still bill memory; usage draws from the plan's included credit. Example from the page: 20 minutes at 1 GB and 30% of a vCPU about $0.03 |
| Free tier | 7-day trial on Developer and Startup plans; a permanent free tier is not listed | Available on Free and Trial plans within included usage: 10 sandboxes per environment at 2 vCPU/2 GB with a 5-minute idle timeout |
| Compliance | Not documented | Not documented |
| Regions | Not documented | US West (default), US East, EU West and Southeast Asia; forks stay in the source region |
| Company headquarters | Not documented | Not documented |
| Good fit for | Teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool | Coding agents and test runs that need to reach your Railway databases and services over the private network |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Depot Sandboxes
- You use Depot CI and want sandbox and agent minutes from the same pool with shared caches
- You want hosted Claude Code, Codex, Devin or Amp sessions that survive closing your laptop
- You need sandboxes on your Tailscale tailnet to reach private services
- You want Arm as well as x86 microVMs
Reasons to choose Railway Sandboxes
- You run services on Railway and want agents to test against them over the private network
- You need forks and checkpoints to try approaches in parallel
- You want Docker inside the sandbox without configuration
- You want EU and Asian regions as well as US
Trade-offs to check first
- Depot Sandboxes: Snapshots save files only, not processes or memory; a stopped sandbox cannot be restarted
- Depot Sandboxes: TypeScript-only SDK, and it was private beta at announcement
- Railway Sandboxes: Pause/resume is not documented; idle sandboxes are destroyed, and memory continues to bill while idle
- Railway Sandboxes: Hypervisor and compliance are not documented on the sandbox pages
Both are worth piloting with your own image and region. See the full Depot Sandboxes profile and Railway Sandboxes profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Depot Sandboxes or Railway Sandboxes better for AI agents?
What is the difference between Depot Sandboxes and Railway Sandboxes?
Which is open source, Depot Sandboxes or Railway Sandboxes?
How do Depot Sandboxes and Railway Sandboxes isolate code?
How does Depot Sandboxes pricing compare with Railway Sandboxes?
How long can sessions run on Depot Sandboxes and Railway Sandboxes?
Do Depot Sandboxes and Railway Sandboxes support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Depot Sandboxes vs Railway Sandboxes. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/depot-sandboxes-vs-railway-sandboxes/