CreateOS Sandbox vs Latitude.Sh
Latitude.sh is the better fit for dedicated CPU or multi-GPU hardware in many regions, automated with an API and Terraform. CreateOS Sandbox is the better fit for small, short-lived isolated environments per agent task, billed per second. Latitude's smallest VM is 4 vCPU / 16 GB, while a CreateOS sandbox can be 1 vCPU / 1 GB.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Latitude.sh 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
- Compute
- $0.0362 /vCPU-hr
- Memory
- $0.0116 /GiB-hr
Latitude.sh
Latitude.sh lists vm.small (4 vCPU, 16 GB, 160 GB) from $0.09/hour or $69/month and g3.h100.small (1x H100) from $1.68/hour, taxes included, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Latitude.sh has the edge.
Smaller units: a 1 vCPU / 1 GB sandbox billed per second, where Latitude's smallest VM is 4 vCPU / 16 GB billed hourly.
Paused CreateOS sandboxes stop vCPU billing; Latitude says shutting down a VM does not pause billing.
Egress allowlists without installing anything in the VM; Latitude's firewall is an opt-in, agent-based UFW service.
Where Latitude.sh is strong
Whole single-tenant servers and multi-GPU machines created and deleted by API with hourly billing, 20 TB of free outbound traffic per server, SOC 2 Type 2 for Security (vendor-stated) and 26 locations worldwide.
Which to Pick
Pick CreateOS Sandbox if
- Each agent task needs a small isolated machine for minutes, not a server for a month.
- You want to pause and fork environments with memory kept.
- You want egress rules enforced outside the VM, not by an agent installed inside it.
Pick Latitude.sh if
- You need dedicated bare metal or 8x B300 GPU machines.
- You need presence in Latin America, Asia-Pacific or many US metros.
- You push heavy outbound traffic and want 20 TB per server included.
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 | Latitude.sh |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | Bare metal: single-tenant. VMs: full VM. AMD SEV on some metal plans |
| Create and destroy by API | Yes: REST API, CLI, MCP server and SDKs for TypeScript, Go, Python, Rust, C# and Java (all but TypeScript pre-1.0) | Yes: REST API, lsh CLI, TypeScript, Go and Python SDKs, Terraform |
| Memory snapshot (pause and resume) | Yes: disk, memory and CPU state saved; vCPU stops billing, memory and storage still bill | Not documented; VM backups copy the disk; stopped VMs keep billing |
| Fork | Yes: fork a paused sandbox into many independent sandboxes | VMs only: restore a backup into a new VM; no live fork |
| Outbound network controls | Open with no rules; deny-by-default once any host, IP, CIDR or wildcard rule exists, enforced on the host outside the VM | Opt-in UFW-based firewall agent with inbound and outbound rules by IP and port |
| Billing granularity | Per second while running: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, storage $0.0001584/GB-hr | Hourly on demand; monthly and yearly reserved discounts |
| Largest size | 8 vCPU / 16 GB on Enterprise; 8 vCPU / 8 GB on Pro | c4.metal.large 96 cores / 384 GB; VMs up to vm.xlarge 32 vCPU / 128 GB |
| GPU | None; no GPU shapes | Yes: 8x HGX B300, 8x RTX PRO 6000, 1x H100 |
Common Questions
How fast does a Latitude.sh server deploy?
Latitude says some operating systems deploy in under 10 seconds with instant deployment, while standard deployment takes about 10 minutes and Windows 15 to 20 minutes (vendor-stated). Its homepage and pricing FAQ quote around 5 seconds, so the figure differs by page.
Does Latitude.sh charge for outbound traffic?
Up to a point. Each server includes 20 TB of free outbound traffic pooled per region, inbound is free, and overage is $0.01 per GB. CreateOS has no per-GB egress fee, with a 50 GiB outbound budget per sandbox by default.
Is a stopped Latitude.sh VM billed?
Yes. Latitude's VM docs say shutting down a VM does not pause billing, and monthly on-demand servers are not pro-rated if deleted early. A paused CreateOS sandbox stops vCPU charges and keeps billing memory and storage per second.
Sources
Checked 17 October 2026.
- Latitude.sh: plans, prices, bandwidth, deploy time, SOC 2
- Latitude.sh: products, tooling, location count
- Latitude.sh: regions
- Latitude.sh: start time
- Latitude.sh: egress / firewall
- Latitude.sh: billing model
- Latitude.sh: quotas
- Latitude.sh: VM deploy, SSH, billing while stopped
- Latitude.sh: persistence / clone
- Latitude.sh: SDKs
- Latitude.sh: products, DDoS, networking features
- CreateOS Sandbox pricing
- CreateOS egress rules
- CreateOS Sandbox limits
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.