Is your organization AI ready? Take the 3-minute test

CreateOS Sandbox vs Together Code Sandbox

Pick Together Code Sandbox if you already use Together AI for inference or training and want sandboxes for RL environments on the same account. Pick CreateOS Sandbox if you want to start without an access request, at lower per-hour rates, with an outbound allowlist you can read in the docs.

The together-sandbox SDK and CLI must be enabled for your organization by request to Together AI.

Pricing at a Glance

CreateOS rates verified 17 October 2026. Together Code Sandbox 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
No egress fees, 50 GiB bandwidth budgetvCPU stops billing while paused

Together Code Sandbox

Compute
$0.0446 /vCPU-hr
Memory
$0.0149 /GiB-hr

Together charges $0.0446 per vCPU-hour and $0.0149 per GiB-hour for Code Sandbox, and $0.03 per 60-minute Code Interpreter session, as of 17 October 2026.

Where CreateOS Sandbox Fits Better

What CreateOS Sandbox brings to this matchup, with a plain note on where Together Code Sandbox has the edge.

Self-serve sign-up with a Free plan; Together enables its sandbox SDK per organization on request.

Lower rates: $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour against $0.0446 and $0.0149.

Where Together Code Sandbox is strong

Together offers sandboxes from the same vendor that serves open-model inference and GPU clusters, with snapshots built remotely from any Docker image or Dockerfile and optional memory snapshots at termination, aimed at RL rollouts and agent tool calls.

Which to Pick

Pick CreateOS Sandbox if

  • You want to start today without an access request.
  • You need documented egress controls and concurrency limits.

Pick Together Code Sandbox if

  • Your inference or training already runs on Together AI.
  • You need up to 16 cores and 128 GB of memory per sandbox.

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.

DimensionCreateOS SandboxTogether Code Sandbox
IsolationFirecracker micro-VM with its own guest kernel, root filesystem and network identityVM per sandbox; hypervisor not named for the new SDK
Pause and resumeSaves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still billEphemeral by default; a termination policy can snapshot the filesystem, optionally with memory
ForkFork a paused sandbox into many independent copies, each with its own id and IPCreate new sandboxes from any snapshot alias; no live fork documented
Outbound network defaultOpen with no rules; deny-by-default once any host, IP, CIDR or wildcard rule exists, enforced on the host outside the VMNot published
Largest size8 vCPU / 16 GB on Enterprise (Pro 8 vCPU / 8 GB, Beginner 4 / 4, Free 1 / 1)16 CPU cores with 1 to 8 GB per core (up to 128 GB)
Session lengthNo lifetime cap; optional idle auto-pause from 60 s to 24 h, off by defaultNo automatic limit unless a ttl is set
BillingPer second: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, storage $0.0001584/GB-hr; no egress fees, 50 GiB bandwidth budget per sandbox$0.0446 per vCPU-hour and $0.0149 per GiB-hour

Common Questions

How do I get access to Together Code Sandbox?

You ask Together AI to enable it: the together-sandbox SDK and CLI must be turned on for your organization by contact. CreateOS Sandbox needs no request; the Free plan comes with 500 credits and no card.

What does Together Code Sandbox cost per hour?

$0.0446 per vCPU-hour and $0.0149 per GiB of RAM per hour, per Together's pricing page. CreateOS Sandbox lists $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, billed per second on every plan.

Can Together Code Sandbox save memory when it stops?

Yes, through a termination policy that snapshots the filesystem and can include memory under an alias, so a new sandbox continues from it. CreateOS Sandbox pause saves disk, memory and CPU state and can resume the same sandbox or fork it into copies.

See CreateOS Sandbox for yourself

Book a demo, or explore the Sandbox and its pricing.