Skip to main content
Superserve runs sandboxes billed per second for vCPU and memory. CostGraph reads Superserve at a grain of one record per resource per day. Spend is Superserve’s own figure before credits, taxes and payments.

​
Choose how the data reaches us

CostGraph pulls it

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

You push it

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

​
Before you begin

  • In Superserve, create a team API key with billing read access.
  • The connect form links to the page where you create this credential.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Superserve.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Superserve 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 Superserve 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 Superserve 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

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