CreateOS Sandbox vs LangSmith Sandboxes
LangSmith Sandboxes make sense if you already use LangSmith or Deep Agents and want execution next to tracing and evals, with snapshots, forks and a credential-injecting auth proxy. CreateOS Sandbox makes sense if you want lower per-hour rates, egress rules you set yourself on any plan, and SDKs beyond Python and TypeScript.
Pricing at a Glance
CreateOS rates verified 17 October 2026. LangSmith Sandboxes pricing as published on 17 October 2026. Rates billed per GB rather than per GiB, or as bundled sizes, are quoted as published rather than converted.
CreateOS Sandbox
Lower compute rate- Compute
- $0.0362 /vCPU-hr
- Memory
- $0.0116 /GiB-hr
LangSmith Sandboxes
- Compute
- $0.0576 /vCPU-hr
- Memory
- $0.0185 /GiB-hr
LangSmith Sandboxes bill 0.0576 LSU per vCPU-hour, 0.01845 LSU per GiB-hour and 0.000123 LSU per GiB-hour of storage, per second, where 1 LSU = $1, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where LangSmith Sandboxes has the edge.
Lower list rates: $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour against 0.0576 and 0.01845 LSU.
You choose the egress policy on every plan; LangSmith applies a restricted allowlist to non-Enterprise organizations by default.
No idle shutdown unless you set one; LangSmith's idle TTL defaults to 600 seconds.
Official SDKs in six languages, compared with Python and TypeScript.
Where LangSmith Sandboxes is strong
Sandboxes sit inside LangSmith next to tracing and evals, so Deep Agents users get execution, snapshots, forks and credential-safe outbound calls in the same account and SDK.
Which to Pick
Pick CreateOS Sandbox if
- You are not on LangSmith and want a standalone sandbox API.
- Your non-Enterprise agents need outbound access beyond a fixed allowlist.
- You want sandboxes to stay up with no idle TTL by default.
Pick LangSmith Sandboxes if
- You trace and evaluate agents in LangSmith and want sandboxes in the same account.
- You need up to 16 vCPU and 64 GiB in one sandbox.
- You want an auth proxy that injects credentials into outbound calls.
Head-to-Head Comparison
Every dimension side by side, checked on 17 October 2026 against each vendor's own docs and pricing pages. "Not published" means we could not find it on the vendor's pages, not that the feature is missing.
| Dimension | CreateOS Sandbox | LangSmith Sandboxes |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | Micro-VM (vendor-stated: dedicated VM); hypervisor not named |
| Pause and resume | Pause saves disk, memory and CPU state; vCPU stops billing, memory and storage still bill | Stop on idle keeps disk; snapshot a running sandbox with optional memory; stopped sandboxes deleted after up to 30 days |
| Fork | Yes, fork a paused sandbox into many independent copies | Yes, fork a snapshot into multiple sandboxes |
| Outbound network default | Open with no rules; deny-by-default once any host, IP, CIDR or wildcard rule exists, enforced on the host outside the VM | Restricted allowlist (PyPI, npm, GitHub, model APIs) for non-Enterprise orgs by default; auth proxy injects credentials |
| Inbound access | Closed by default; opt-in public HTTPS URL | Authenticated service URL per port; TCP tunnels to a local machine |
| Largest size | 8 vCPU / 16 GB on Enterprise; 8 vCPU / 8 GB on Pro | Up to 16 vCPU, 64 GiB memory, 64 GiB filesystem |
| Concurrency | 1 / 5 / 20 / 30 by plan; paused sandboxes count toward the cap | Free allowance limited to 10 sandboxes; bursts to thousands (vendor-stated) |
| Session length | No cap; idle auto-pause 60 s to 24 h, off by default | Idle TTL 600 s by default; no hard maximum published |
| Billing | Per second: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour, storage $0.0001584 per GB-hour; no egress fees, 50 GiB bandwidth budget per sandbox | Per second: 0.0576 LSU per vCPU-hour, 0.01845 LSU per GiB-hour (1 LSU = $1) |
| Self-host or BYOC | Enterprise only, onboarded by our team | Yes, on self-hosted LangSmith (Kubernetes) with a license that includes sandboxes |
Common Questions
What is the default network policy for LangSmith Sandboxes?
For non-Enterprise organizations, LangSmith docs describe a restricted allowlist covering PyPI, npm, GitHub, OpenAI, Anthropic and LangSmith. CreateOS Sandbox starts open with no rules and becomes deny-by-default once you add any rule, on every plan.
Do LangSmith Sandboxes shut down when idle?
Yes, by default. idle_ttl_seconds is 600 seconds unless set to 0, and commands with no client attached are killed after one hour by default. CreateOS Sandbox idle auto-pause is off unless you set it between 60 seconds and 24 hours.
Can I self-host LangSmith Sandboxes?
Yes, on self-hosted LangSmith running on Kubernetes, with an instance license that includes sandboxes. CreateOS Sandbox self-hosting and BYOC are enterprise-only and onboarded by our team rather than installed by you.
What does 1 LSU cost in LangSmith?
One LSU equals $1. LangSmith Sandboxes bill 0.0576 LSU per vCPU-hour and 0.01845 LSU per GiB-hour, per second, and the pricing page includes 8 LSU of sandbox usage per month, limited to 10 sandboxes.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.