Integrations3 min read
CostGraph launches support for Autumn
CostGraph now exports tenant compute usage as billable meters to Autumn, so usage-based SaaS can bill on the same container, runtime, CPU, and memory data they use to monitor costs.
By CostGraph Team
ChatGPTUsage-based billing for compute is awkward. A SaaS provider running customer workloads has to know, per tenant, how many containers ran, for how long, and how much CPU and memory they actually consumed. The usage lives in the platform. The invoice lives in the billing system. Getting one to the other usually means scripts, spreadsheets, and a reconciliation meeting at the end of the month.
Autumn has won the hearts of some of our biggest customers and for good reason: metered plans, entitlements, invoices. What it needs is a source of usage that is accurate down to the workload. That is the part we are good at, so we wired the two together.
Today we are launching support for Autumn. CostGraph tracks compute usage per tenant and exports it to Autumn as billable meters, so the usage your customers generate and the usage you bill them for come from the same place.
CostGraph indexes your infrastructure the way it always has: nodes, pods, containers, and the cost data behind them. The integration profiles each workload on the nodes it actually runs on, then converts usage into dollar values using VM and Spot VM hourly pricing.
Profiling also makes spend assignable. Because every workload is tied to the customer it serves, you can split one provider bill into multiple line items, one per customer, each reflecting the containers, runtime, CPU, and memory that customer actually used. CostGraph exports those line items to Autumn, and each lands as its own line on the customer's invoice.
Assignment is done with virtual tags, which we launched earlier this week. You define one rule per customer, and the resources the tags claim become that customer's line items. Nothing is written back to your infrastructure, and Graph AI can draft the rules from a plain English description.
CostGraph remains in your product lifecycle the way an SDK or an API call would.
Check out the docs to get started.
If this sounds useful, get started for free or book a demo today.
Frequently Asked Questions
CostGraph can now export usage data to Autumn.
Teams already use CostGraph to track cloud and Kubernetes costs. The integration turns that same usage data into billable meters in Autumn, so usage-based SaaS providers can bill on compute without building the tracking themselves.
The Autumn integration is available on all CostGraph plans today.
CostGraph tracks compute usage per tenant, converts it to billable quantities, and exports usage events to Autumn. Autumn applies the entitlements you configured and produces the invoice.
CostGraph is the metering source. Autumn is the billing system.
Two things. Create a virtual tag for each customer, so CostGraph knows which workloads belong to whom. Then connect Autumn and provide an API key scoped to writing usage events. The docs walk through the connection step by step.
The initial meters are container count, runtime, CPU core-hours, and memory gigabyte-hours, valued against VM and Spot VM hourly pricing.
CostGraph requires an Autumn API key scoped to writing usage events for your Autumn project.
CostGraph does not need access to your payment provider. Entitlements, invoices, and dunning stay in Autumn.
CostGraph exports usage once per UTC day, skipping the current incomplete day.
CostGraph exports usage from the moment the integration is connected. Earlier periods are not backfilled.
No. CostGraph meters usage and hands it to Autumn. Entitlements, invoicing, and payment collection happen in Autumn, using your existing configuration there.
Yes. The exported meters come from the same model CostGraph uses for cost tracking, so you can group consumption and spend by tenant, service, or node inside CostGraph while Autumn bills the same numbers.