Skip to main content
Runloop devboxes are isolated VMs for coding agents. CPU and memory are billed per second while a devbox runs, and disk for as long as it exists. CostGraph reads Runloop at a grain of one record per devbox per day for CPU, memory and disk. Spend is estimated from Runloop’s published prices and your plan, and can differ from your invoice.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we read Runloop. Nothing to run.

You push it

You send us the records over the API. Your credentials stay in your infrastructure.

​
Before you begin

  • In the Runloop dashboard, create an API key.
  • Pick your plan on the connect form: Basic (the default, 100 GB of free storage), Pro (1 TB of free storage and its monthly fee) or Enterprise. On Enterprise, also enter the free storage your contract includes.
  • The connect form links to the page where you create this credential.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Runloop.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Runloop needs and marks the optional ones.
  4. Select Connect.
CostGraph verifies the credentials with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Credentials are encrypted at rest and used only to read usage and cost. Revoke them in Runloop at any time and the connection stops; nothing else is affected.

​
Push it yourself

Send the charges to CostGraph yourself instead. Push data covers the connection id, the focus:write key, and the request shape.

​
Run the exporter

Your Runloop credential stays with you. Only the finished records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

​
What CostGraph does with it

Runloop spend appears in Cost Overview and in anomaly detection alongside every other provider.