Reference
# Limits
> The size of a sandbox, how many a workspace can run and keep, its network, and the size limits of each route.
Need more than these? [Write to us](mailto:support@superhq.ai).
## A sandbox
| Resource | Size |
| -------- | -------------------------- |
| CPU | 2 vCPU, arm64 |
| Memory | 2 GiB |
| Disk | 20 GiB |
| System | Debian 13, running as root |
## Network
| What | Limit |
| ----------------------------- | ----------------------------------------------- |
| Data sent out | 100 Mbit/s per sandbox, all connections at once |
| Data coming in | Not limited |
| Mail ports 25, 465, 587, 2525 | Refused; send mail through an email API |
| Addresses reached | Public internet only |
New connections are paced, so a scan or a flood slows down while installs and page loads do not notice.
## A workspace
| Limit | Value | Refusal |
| ------------------------- | ----------- | --------------------------------------- |
| Sandboxes kept, any state | 100 | `429 sandbox_limit_exceeded` |
| Sandboxes running at once | 10 | `429 concurrent_sandbox_limit_exceeded` |
| Sandboxes created | 30 a minute | `429 sandbox_creation_rate_limited` |
The running limit counts sandboxes that are running or starting. It applies to creates and to wakes. A sandbox stops after 30 idle seconds, which frees its place. The list route answers your current counts and limits.
## Timing
| What | Value |
| ----------------------------------------- | ---------- |
| Idle time before a sandbox stops | 30 seconds |
| Time to send the target on a proxy socket | 10 seconds |
## Requests
| What | Limit |
| ---------------------------------- | ----------------- |
| Exec stdin over HTTP | 10 MiB |
| Session output kept for replay | 1 MiB per session |
| File write | 16 MiB |
| Paths followed by one watch socket | 8 |
| Checkpoint comment | 1024 bytes |
| Sandbox name | 63 characters |
| List page | 500 sandboxes |
## Environment and secrets
| What | Limit |
| -------------------------------- | -------------- |
| Variables per sandbox | 100 |
| Secrets per sandbox | 50 |
| Hosts per secret | 20 |
| One value | 32 KiB |
| Names, values and hosts together | 256 KiB |
| Name | 128 characters |
Limits
The size of a sandbox, how many a workspace can run and keep, its network, and the size limits of each route.
Need more than these? Write to us.
| Resource |
Size |
| CPU |
2 vCPU, arm64 |
| Memory |
2 GiB |
| Disk |
20 GiB |
| System |
Debian 13, running as root |
| What |
Limit |
| Data sent out |
100 Mbit/s per sandbox, all connections at once |
| Data coming in |
Not limited |
| Mail ports 25, 465, 587, 2525 |
Refused; send mail through an email API |
| Addresses reached |
Public internet only |
New connections are paced, so a scan or a flood slows down while installs and page loads do not notice.
| Limit |
Value |
Refusal |
| Sandboxes kept, any state |
100 |
429 sandbox_limit_exceeded |
| Sandboxes running at once |
10 |
429 concurrent_sandbox_limit_exceeded |
| Sandboxes created |
30 a minute |
429 sandbox_creation_rate_limited |
The running limit counts sandboxes that are running or starting. It applies to creates and to wakes. A sandbox stops after 30 idle seconds, which frees its place. The list route answers your current counts and limits.
| What |
Value |
| Idle time before a sandbox stops |
30 seconds |
| Time to send the target on a proxy socket |
10 seconds |
| What |
Limit |
| Exec stdin over HTTP |
10 MiB |
| Session output kept for replay |
1 MiB per session |
| File write |
16 MiB |
| Paths followed by one watch socket |
8 |
| Checkpoint comment |
1024 bytes |
| Sandbox name |
63 characters |
| List page |
500 sandboxes |
| What |
Limit |
| Variables per sandbox |
100 |
| Secrets per sandbox |
50 |
| Hosts per secret |
20 |
| One value |
32 KiB |
| Names, values and hosts together |
256 KiB |
| Name |
128 characters |