Beam
Container sandboxes with optional GPUs, filesystem and memory snapshots, started from Python or TypeScript and billed per millisecond per physical CPU core and GiB of memory.
Operated by Smartshare, Inc. www.beam.cloud Status: active[1] Checked 31 Oct 2026
Agent sandboxes
Beam Sandboxes
- Price
- $0.135 /core (2 vCPU)-h
- + $0.023 per GB-hour
- Fleet month
- ≥ $2,019
- 50 × 8 h × 22 days
- Billed on
- Running time
- per second
- Isolation
- Container
- sessions up to Unlimited
What to know
- $20/mo planThis price only applies on a plan of at least $20 a month.
Plans
Prices
| Resource | Price | Per hour |
|---|---|---|
| per core (2 vCPU) | $0.0000375 /s[1] | $0.135 |
| per GB of memory | $0.0000064 /s[1] | $0.023 |
- Sandbox rates: $0.0000375/s per physical core (2 vCPU equivalent, about $0.135/h) and $0.0000064/s per GiB of RAM, billed per millisecond while the sandbox runs. The only size listed here is the pricing page's worked example (1 core / 8 GiB = $0.319/h).
- Sandbox defaults are 1 CPU, 128 MiB of memory and a 600-second lifetime; GPUs can be attached (gpu, gpu_count), but no sandbox-specific GPU rate is published.
- Filesystem snapshots become images for new sandboxes; memory snapshots capture processes and exposed ports and restore into new sandboxes.
- "Sandboxes cold boot in one to three seconds" is a vendor claim from the sandbox page.
- Beam also sells persistent VMs (no GPUs, browser desktop, SSH, pause/fork) at $0.0252/h per vCPU and $0.0054/h per GiB, billed per second, with a 50 GiB root disk; they are not part of this record.
- Growth plan (1,000+ GPU containers, unlimited CPU containers) is priced on request. BYOC charges a management fee of $0.019/h per vCPU and $0.009/h per GB.
- The open-source runtime behind Beam is Beta9; self-hosting it does not include every Beam Cloud feature.
- No egress or bandwidth fees on any plan; snapshots are included.
Terms
Billing
Runtime
Lifecycle
- Survives a stop
- Nothing (ephemeral)[3]
- Snapshots
- Yes[3]
- Pause and resume
- unknown[3]Sandbox docs describe memory snapshots and restore, not pause; pause is documented for Beam VMs
- Fork
- Memory and processes[3]
- Compute billed while stopped
- unknown[3]Sandboxes have no paused state; billing runs while the sandbox runs
- Auto-stop
- after 10 min[3]
- Start time (vendor claim)
- 3 s[3]
Capabilities
Storage and network
Platform
Sources
- 1 beam.cloud/pricing · 31 Oct 2026
- 2 docs.beam.cloud/v2/self-hosting/overview · 31 Oct 2026
- 3 docs.beam.cloud/v2/sandbox/snapshots · 31 Oct 2026
- 4 docs.beam.cloud/v2/sandbox/overview · 31 Oct 2026
Raw data: JSON