Skip to main content
This is feature is only available if you are on the Enterprise tier or above. See Astro Plans and Pricing.
Does your platform team own the Astro contract while other teams use Astro through their own Workspaces or Deployments? If so, you need a repeatable way to split that shared cost across teams. Organization dashboards show you Astro credit usage and who’s using it, but they don’t build a chargeback report for you. This guide walks you through turning that dashboard data into a chargeback report. It covers the following steps:
  • Choose how you attribute credit usage to teams: by Workspace, by Deployment, or both.
  • Adjust reported credit usage for your contract’s discount, since dashboards report list-price figures by default.
  • Attribute Workspace and Deployment credit usage using the Cost Breakdown dashboard.
  • Attribute shared infrastructure credit usage, like a dedicated cluster that multiple Workspaces share.
  • Account for teams with different usage patterns. Some teams run Dags often, and others run them rarely.
  • Automate recurring chargeback reporting instead of pulling data manually each cycle.
  • Pull the same credit usage data programmatically using the Billing API.
Repeat this process each billing cycle to keep your chargeback reports consistent as teams, Workspaces, and Deployments change.

​
Relevant dashboards

All dashboard and export figures are in USD.

​
Prerequisites

This guide assumes that you have:
  • Organization Billing Admin user permissions.
  • At least one Astro Workspace per team you want to attribute credit usage to, or an equivalent naming convention that maps Workspaces or Deployments to teams.

​
Build your chargeback report

1

Choose your attribution model

Decide how you map credit usage data to teams before you pull any reports:
  • Attribute credit usage by Workspace: base each team’s credit usage on the Workspace or Workspaces that team owns. This works well when each team has dedicated Workspaces.
  • Attribute credit usage by Deployment: attribute credit usage at the Deployment level when a single Workspace contains Deployments that belong to different teams.
  • Attribute credit usage by both: use Workspace as the primary attribution unit and Deployment as a secondary breakdown when a team needs credit usage detail for individual pipelines.
The model you choose determines which tab you use in the next step.
2

Adjust for your contract discount

The Cost Breakdown, Clusters, Worker Queues, and Underlying Data dashboards all report credit usage at Astronomer’s list price for your Organization’s tier. If your contract includes a discount, that discount doesn’t appear in these figures.
  1. On the Contract Details tab, use the Viewing As control to note the Current Contract Balance under both Cost Basis and Credits.
  2. Divide the Cost Basis balance by the Credits balance to calculate your discount factor. For example, a Cost Basis balance of $49,500 against a Credits balance of $50,000 gives a discount factor of 0.99, meaning your contract has a 1% discount.
  3. Multiply the credit usage figures from these dashboards by your discount factor before you charge a team.
Recalculate your discount factor each time you build a chargeback report, since it can change at contract renewal. See Track credit usage against your contract for more on monitoring your overall contract balance.
3

Attribute Workspace and Deployment credit usage

  1. In the Astro UI, click Dashboards, then click the Cost Breakdown tab.
  2. Use the Time Period, Workspace Name, and Deployment Name filters to scope the dashboard to the billing period you’re reporting on.
  3. Review the Workspace Cost chart to compare total credit usage across teams at a glance.
  4. Under Detailed Costs, click Deployments to see credit usage broken down by Workspace Name, Deployment Name, and billable item. Click Compute Types for the same breakdown by compute type, if a team needs to understand what’s driving their compute usage.
The Detailed Costs tables include Workspace Name and Deployment Name filters, so you can isolate a single team’s credit usage before exporting it to share with that team.
4

Attribute shared infrastructure credit usage

Dedicated clusters are often shared by multiple Workspaces, so their credit usage doesn’t attribute directly to a single team through the Deployments or Compute Types breakdowns.
  1. On the Cost Breakdown tab, under Detailed Costs, click Clusters.
  2. Review the credit usage breakdown by Cluster Name and Workspace Name, which splits cluster credit usage into dedicated cluster cost, disaster recovery cluster cost, disaster recovery replication cost, and network cost.
  3. Sum the dedicated cluster cost and network cost for each cluster. Network chargeback cost comes from the dedicated cluster, so allocate the two together rather than as separate line items.
  4. Divide each cluster’s combined credit usage across the Workspaces that use it, based on the attribution model you chose in the first step. For example, split credit usage evenly across consuming teams, or weight it by each team’s usage from the next step.
The Clusters breakdown excludes Workspace credit usage that can’t be tied to a specific cluster, such as AI token usage. Attribute that credit usage using the Deployments or Compute Types breakdown instead.
Some credit usage figures take time to fully populate. Network credit usage in particular can take a couple of days to arrive, so a chargeback report you build right after a billing period ends might report a lower network credit usage than it should.
Worker queue credit usage only applies to Deployments running the Celery Executor or Astro Executor. Use the Worker Queues tab under Detailed Costs if a team needs credit usage broken down by individual worker queue.
5

Account for different usage patterns

Splitting shared credit usage evenly across teams can be inaccurate if some teams run Dags far more frequently than others. Compare usage before you finalize an allocation:
  1. Click the Organization Overview tab and review Top 10 Workspaces by Active Dag Count and Top 10 Workspaces by Code Deploy Count to see which teams drive the most activity.
  2. Click the Operator Use tab and filter by Workspace Name to compare task counts and Dag counts for each team.
  3. Use these usage numbers to weight the shared credit usage allocation from the previous step. For example, a team responsible for 70% of task runs on a shared cluster takes on 70% of that cluster’s credit usage, rather than an even split.
6

Automate recurring chargeback reporting

Instead of pulling each dashboard manually every billing cycle, export chargeback data on a schedule.
  1. Click the Underlying Data tab to see the Daily Cost Breakdown table, along with the same data in the FinOps Open Cost and Usage Specification (FOCUS) format, a standardized billing schema that’s easier to load into an existing chargeback or finance tool.
  2. See Export Astro reporting data to set up a recurring export or a conditional dashboard alert for this table.
Astronomer recommends scheduling exports from the Underlying Data tab instead of from individual charts, since it gives you a consistent, standardized format each cycle.
7

Pull chargeback data with the Billing API

LabsThis feature is in Labs.
Instead of exporting from the UI, pull the same credit usage data programmatically with the Astro API. This is useful if you want to load chargeback data directly into your own finance or BI tooling. See the Astro Labs API overview for authentication, base URL, and versioning details. The Billing API is available on the Enterprise tier and above, and requires the same Organization Billing Admin-level permission as the rest of this guide.Use the following endpoint:
  • GET /organizations/{organizationId}/billing/daily-usage: provides fine-grained Astro credit usage data on a daily time grain. Corresponds to the Daily Cost Breakdown table on the Underlying Data tab by default, or the FOCUS Format table when you set format=focus to get the same data in the FinOps FOCUS format.
This endpoint accepts startDate and endDate query parameters, workspaceId and deploymentId filters for scoping to specific teams, and limit/offset pagination:
Usage data can be delayed, so exporting only the previous day’s data might not capture every cost row accurately. Export daily to keep your data current, but query a 7-day lookback window each time (for example, set startDate to 7 days before endDate) so any rows that arrived late get included in your chargeback calculations.

​
Track credit usage against your contract

After you attribute credit usage to teams, use the Contract Details tab to monitor your Organization’s overall credit or dollar balance and projected burn rate. This dashboard reports credit usage at the Organization level and isn’t team-attributable on its own, but it’s useful context for the central team responsible for procurement when reviewing chargeback totals against the overall contract. Set the Viewing As control to Cost Basis when you reconcile chargeback totals against the overall contract, since it reflects what your Organization actually paid rather than list-price Credits.