WBX Sandbox
Reference

Limits

All limits in one place. When a limit is reached the API answers with an error that says which one – usually 429 for plan limits and 400 for a request that is too large.

Your plan

How many sandboxes you can run at once, their vCPU and memory, their maximum lifetime and the templates you can use depend on your plan – see pricing. Sleeping sandboxes do not count towards the concurrent-sandbox, vCPU and memory limits.

Sandboxes

WhatLimit
Command output (exec)16 MB per stream; longer output is cut off (truncated: true)
Output kept for background processesthe last 1 MB per stream
Sleeping sandboxkept 7 days without use, then deleted; may move to long-term storage after about a day
Idle time before an MCP sandbox falls asleep10 minutes by default (idle_timeout_s 60–604800 for your own sandboxes)
Terminals10 open per account; an idle terminal closes after 30 minutes
Directory listing depth5
Namelowercase letters, digits, . _ -, up to 63 characters

Jobs and batches

WhatLimit
Job time limit (timeout_s)default 3600 s, at most 86400 s
Result files100 per job, 100 MB each, 512 MB per job; 5 GB stored per team
How long results are kept7 days (log, result files and receipt)
Input files (inputs)32 files and 64 MB per job
Jobs in one batch1–1000
Jobs of one batch running at the same time1–100 (max_concurrency, default 10); submit more batches for more
Waiting on the server (POST /v1/jobs/wait)up to 60 s per call
Listing200 jobs or 100 batches per page

WebAssembly jobs

Module up to 8 MB inline (up to 32 MB as an input), memory 16–1024 MB, time up to 10 minutes, stdin up to 4 MB, 64 output files (64 MB together). See WebAssembly jobs.

When a limit is reached

The error codes and what to do about them are listed in REST API → Errors. Spending limits for jobs are a separate feature – see Budgets.