Skip to main content
Hatchet Cloud is a distributed task queue for durable execution, billed on the task runs it executes. CostGraph reads Hatchet Cloud as FOCUS 1.2 records at a grain of one record per tenant per day.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Hatchet Cloud 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 Hatchet, go to Settings > API Tokens and create a client token for each tenant you want to export. A client token is scoped to one tenant and carries its own server URL, so nothing else identifies the deployment.
  • Note your plan’s included run allowance and platform fee if you want runs priced. Hatchet’s API returns usage, not cost.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Hatchet Cloud.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Hatchet Cloud 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 Hatchet Cloud 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 Hatchet Cloud 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 Hatchet Cloud 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 Hatchet Cloud spend appears in Cost Overview and in anomaly detection alongside every other provider, so failed task runs that bill the same as successful ones stand out as waste.