Skip to main content
Daytona runs cloud development environments as sandboxes. A started sandbox bills compute and disk; a stopped or archived sandbox bills disk only. CostGraph reads Daytona as FOCUS 1.2 records at a grain of one record per sandbox per day.

Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Daytona once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

Before you begin

  • In the Daytona dashboard, go to Keys and create an API key.
  • Note the organization id to scope the export to one organization. Leave it empty and the key’s default organization is used.
  • The connect form links to the page where you create this key.

Let CostGraph pull

  1. Open Settings > Integrations and pick Daytona.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Daytona 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 billing data. Revoke them in Daytona at any time and the connection stops; nothing else is affected.

Push it yourself

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

Run the exporter

Rather than build that request yourself, run our exporter. It reads Daytona on a schedule and pushes the records for you, wherever you want to run it: a container, a Kubernetes CronJob, or a binary on a machine you already have.
Your Daytona credential stays where you put it, and only the finished FOCUS records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there Daytona spend appears in Cost Overview and in anomaly detection alongside every other provider, so started-but-idle sandboxes stand out as waste.