SB-Box plans, limits and billing

SB-Box bills the same Genspark credit balance as every other product. This page is the whole story: the rates, your plan's limits, how debits land, what happens when credits run out, and where to see and top up. The user guide is at /sb-box/docs; this page as markdown: /sb-box/billing.md.

1. Rates: what you pay and when

Resource	Credits	Per	Charged while
CPU	25	vCPU-hour	the sandbox is running
Memory	8	GB-hour	the sandbox is running
Disk	0.05	GB-hour	the sandbox or template exists (running or frozen), until it is killed / deleted

Templates bill disk only: a ready template's diskSizeGB at the disk rate from the moment the build finishes until you delete it. Building a template is not charged, and templates use no CPU or memory.

When your credits run out:

• Your running sandboxes are frozen (disk and memory kept; only the disk keeps billing). Nothing is killed immediately.
• Frozen sandboxes are kept for at most 30 days after your credits run out; add credits before then to keep them.
• create, resume and clone answer 402 sb_box_insufficient_credits until you add credits, and nothing revives a frozen sandbox meanwhile — commands, files, port URLs, reset and rollback answer 402 billing_suspended. Your first call after a top-up lifts it.
• There is no cap on how long a sandbox may run: your balance is the limit.

2. Per-plan limits

Plan	Concurrently running sandboxes	Per sandbox — vCPU · memory · disk	Concurrent template builds
Free	not supported
Plus	50	8 · 8 GiB · 20 GB	5
Pro	100	8 · 16 GiB · 20 GB	5
Team (per member)	100	8 · 16 GiB · 20 GB	5
Enterprise	1,100	8 · 16 GiB · 20 GB	5

3. Seeing your usage

• Console → Usage: your plan and caps, and per-day run time, vCPU-hours, memory GB-hours, disk GB-hours and the credits debited.
• GET /limits: your plan, caps and current counts.
• GET /usage?days=30 (1–366): per-day quantities in seconds and the credits at the current rates.