Skip to content

Limits and defaults

Limit Default Range What happens at the limit
Running at once 5 forks 1 to 500 forkstage up and the GitHub App refuse with “limit reached”; destroy a fork or raise the limit
Idle stop 30 minutes 5 to 1440 a fork with no command, shell or request for that long is destroyed; reason idle stop
Hard stop 8 hours 1 to 168 a fork older than that is destroyed whatever it is doing; reason hard stop

Change them in the dashboard under Settings → Limits (admins).

Default
vCPUs 4 (resources.cpu)
Memory 3 GiB (resources.memory)
Disk copy-on-write from the snapshot; grows as the fork writes
Time to ready about 100 ms after the snapshot is warm on the host
Source size up to 256 MB packed (without node_modules, .git, dist, .venv, target)
Time up to 20 minutes; typical 20 to 60 s
One bake per workspace at a time a second bake waits
Proofs 30 days
Snapshots while the stack exists; the newest is what forks use
Finished environments listed for 24 hours on the dashboard; counted in the month’s numbers

There is no charge during early access and the defaults above apply to every workspace. Paid plans will raise them.