Skip to main content
STACKIT bills per project across its managed services, so spend is attributed per project and service. CostGraph reads STACKIT as FOCUS 1.2 records at a grain of day x project x service.

​
Choose how the data reaches us

CostGraph pulls it

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

You push it

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

​
Let CostGraph pull

  1. Open Settings -> Integrations and pick STACKIT.
  2. Name the connection and pick the tenant these charges belong to.
  3. Fill in the values the form asks for. It lists exactly the variables STACKIT needs, marks which are optional, and explains the permission each one requires.
  4. Select Connect.
The service account key JSON is always required, as a value or a file path. If you created the key from a public key you uploaded, also supply the PEM-encoded private key; keys STACKIT generated already embed it. Given both, the separate private key wins. The service account needs the cost-management.cost.reader role on the customer account you export. 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 STACKIT 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.

​
What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there STACKIT spend appears in Cost Overview and in anomaly detection alongside every other provider.