Skip to main content
Collimate runs hardware-isolated Firecracker microVM sandboxes for agents and RL post-training, with live fork of a running sandbox into many copy-on-write children. The following table shows what CostGraph runs on this provider. CI runners: no. Collimate commands cannot run in the background and stop after 15 minutes, so a runner cannot outlast a short job.

​
Connect

Run the dispatcher with provider set to collimate and these variables:
  • COLLIMATE_API_KEY
If you connected Collimate for cost data, CostGraph’s dispatcher can start sandboxes with the key from your Collimate integration. That key then needs the permissions in the next section as well.

​
Key and permissions

COLLIMATE_API_KEY is a Collimate API key (col_<tier><id><secret>), created in the Collimate console under API keys > Create after signing in with Google or GitHub; shown once, revocable in the console. Keys are not scoped: ‘it carries your tenant’s access’ (full access to the tenant). Tier and limits come from the server-side key record. Sources: docs.collimate.ai: authentication, docs.collimate.ai: limits, docs.collimate.ai: lifecycle.

​
Limits

  • Max session duration: Demo 1 hour, Pro 24 hours, Enterprise unlimited; ‘a sandbox that outlives your tier’s max session is reaped.’ Suspending frees the slot and stops the meter. (source)
  • Concurrent sandboxes: Demo 2, Pro no limit, Enterprise unlimited. (source)
  • Per-sandbox vCPU/RAM caps are not documented; capacity is platform-managed. (source)