CreateOS Sandbox vs Sakura Cloud
Sakura Cloud is the pick for Japanese organisations, including government suppliers, that need servers or H100 GPUs hosted in Japan under ISMAP. CreateOS Sandbox is the pick when agent or untrusted code needs a disposable micro-VM per task, created by API and billed per second. CreateOS runs in eu and us regions, so it does not meet a Japan-only hosting rule.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Sakura Cloud 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
Sakura Cloud
Sakura lists the Standard plan 1 vCPU / 1 GB in Ishikari Zone 1 at 7 JPY/hour, 77 JPY/day or 1,540 JPY/month, with no usage-based transfer charges, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Sakura Cloud has the edge.
Per-second billing; Sakura's billing starts at hourly granularity before moving to daily and monthly caps.
Pause saves memory and CPU state, then fork copies it; Sakura documents disk archives and snapshots only.
Egress rules by hostname, IP or CIDR enforced outside the VM, where Sakura's default outbound policy is not published.
Where Sakura Cloud is strong
Domestic Japanese hosting with ISMAP registration, ISO/IEC 27017 and a SOC 2 Type 1 report (vendor-stated), no per-GB transfer charges, and H100 GPU servers, which suits public-sector and data-residency requirements in Japan.
Which to Pick
Pick CreateOS Sandbox if
- You run agent code per task and want each run isolated and billed per second.
- You need to pause, resume and fork environments with memory intact.
- You can host in the eu or us region.
Pick Sakura Cloud if
- Your data must stay in Japan, or you supply Japanese government systems.
- You need H100 GPU servers in Japan.
- You want transfer volume without usage-based charges.
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 | Sakura Cloud |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | Full VM; hypervisor not named |
| 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 v1.1, usacloud CLI, Terraform provider |
| Memory snapshot (pause and resume) | Yes: disk, memory and CPU state saved; vCPU stops billing, memory and storage still bill | Not documented; disk archives and up to 16 snapshots per dedicated-storage disk |
| Fork | Yes: fork a paused sandbox into many independent sandboxes | No live fork; a disk archive can seed new servers |
| 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 | Per-NIC packet filters with 5-tuple rules; default not published |
| Billing granularity | Per second while running: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, storage $0.0001584/GB-hr | Hourly, then daily, capped monthly; charges stop rising after 20 days in a month |
| Largest size | 8 vCPU / 16 GB on Enterprise; 8 vCPU / 8 GB on Pro | Up to 192 virtual cores and 1,024 GB memory (vendor-stated) |
| GPU | None; no GPU shapes | Yes: H100 and V100, Ishikari Zone 1 only (V100 new creation ends 31 December 2026) |
Common Questions
Is Sakura Cloud approved for Japanese government use?
Sakura Cloud is ISMAP registered (C21-0030-2, first registered 20 December 2021) and was conditionally accepted for Japan's Government Cloud in the FY2023 call (vendor-stated). CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA.
How does Sakura Cloud bill a server used for one hour?
Sakura bills hourly, then daily, then caps at a monthly amount, applying the cheapest rate automatically; a 1 vCPU / 1 GB server in Ishikari Zone 1 is 7 JPY an hour. CreateOS bills each second a sandbox runs, so a 20-minute 1 vCPU / 1 GB run costs about $0.016.
Can I still order V100 GPU servers on Sakura Cloud?
Until 31 December 2026. Sakura says new V100 creation ends then and the V100 service ends on 31 March 2027, while H100 servers remain in Ishikari Zone 1. CreateOS offers no GPU shapes, so GPU work belongs on Sakura or another GPU cloud.
Sources
Checked 17 October 2026.
- Sakura Cloud: plan prices, max shape, zones
- Sakura Cloud: billing model, no transfer charges, no fees until resources added
- Sakura Cloud: GPU prices, V100 retirement, zone
- Sakura Cloud: GPU plan specs
- Sakura Cloud: snapshots
- Sakura Cloud: archives
- Sakura Cloud: packet filter
- Sakura Cloud: Terraform, usacloud
- Sakura Cloud: API
- Sakura Cloud: ISMAP
- Sakura Cloud: SOC 2 Type 1
- Sakura Cloud: ISO 27017
- CreateOS Sandbox pricing
- CreateOS pause, resume and fork
- CreateOS Sandbox limits
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.