Run Cloud no longer offers Linux sandboxes to new organizations.
CI runners: no. AutoPilot compares runners by price, and this provider publishes no sandbox price.
Connect
Run the dispatcher withprovider set to run-cloud and these variables:
RUN_CLOUD_API_KEYorRUN_CLOUD_API_TOKEN
Key and permissions
RUN_CLOUD_API_KEY (RUN_CLOUD_API_TOKEN is an accepted alias) is a run.cloud API key (rc_live_…) created in the run.cloud dashboard; no dashboard path or CLI command is documented. The provider doesn’t document key scopes or roles, so a key has full access to the account. Sources: docs.run.cloud: sandboxes, docs.run.cloud: limits, docs.run.cloud: typescript sdk, docs.run.cloud: install, docs.run.cloud: quickstart.Limits
- DEPRECATED: ‘Linux microVM sandboxes are deprecated. This capability is being retired and is no longer available to new organizations.’ No retirement date given. (source)
- Per sandbox max 32 vCPUs and 112 GiB RAM; default reservation 0.125 vCPU / 128 MiB. (source)
- Org-wide defaults: 100 sandboxes (paused/stopped count), 100 reserved vCPUs, 400 GiB reserved memory; 429 when reached; raise via [email protected]. (source)
- Max lifetime and idle timeout not documented; hitting the spend ceiling stops active sandboxes. (source)