Showback vs Chargeback for Cloud & AI Spend
Show each team what it spent, or bill it back to their budget — which model fits a 20–200 person company, and what has to be true before chargeback works.
- Read-only access
- 14-day free trial
- No credit card required
- 5 min
- setup, per provider
- 90 days
- available history
- Same-day
- anomaly alerts
Daily spend by provider
$24,321 total
See the workflow in practice.
Read-only access, with nothing to install.
Billing integrations read cost and usage data without changing your provider resources. Permissions vary by provider; follow its setup guide. Claude usage uses opt-in OpenTelemetry, and custom sources use cost imports or scoped ingestion rather than a billing API.
How it worksCatch the spike the day it starts.
StackSpend learns what normal looks like per provider, account and service, then flags the day something breaks pattern, with a severity and an owner. Each one carries a lifecycle, so it gets closed.
How it worksOne message each morning. Nobody opens a billing portal.
Team plan and above
How it worksProduct examples are illustrative. Usage estimates and provider-reported costs are separate measures; availability varies by connected source.
Explore the data viewWhy is this spend hard to control?
- Cost sits in one central budget, so no team feels it and the only person incentivised to care is whoever owns the total.
- Chargeback gets proposed before attribution is trustworthy, and the first month is spent arguing about whose spend the shared cluster is.
- Showback becomes a monthly slide nobody acts on, because the numbers arrive after the decisions that caused them.
- Shared infrastructure and shared AI keys have no obvious owner, and that unallocated remainder is where the argument always lands.
Know what you are connecting.
The workflow
- 01
Tag-based allocation gives each team its own view of spend, updated daily rather than compiled monthly — showback that arrives while the decision is still fresh.
- 02
Per-team budgets turn showback into something with teeth without moving any money: each team gets a ceiling and its own 50/80/100 percent alerts.
- 03
Unallocated spend is reported explicitly, so you know exactly how ready you are for chargeback rather than guessing. Coverage is the gate.
- 04
When you do move to chargeback, the same tags and categories export through the API, so finance works from the allocation engineering already trusts.
The source
Billing and usage from your connected providers. Credential types and permission controls vary by provider.
Provider connection guidesThe limits
Provider reporting and scheduled sync determine freshness. Available history and attribution vary by source; review the setup guide for coverage. Alerts notify your team; they do not block requests or enforce a spending cap.
What we track
- Spend per team, product, and environment
- Per-team budgets with threshold alerts
- Allocation coverage and unallocated remainder
- Daily per-team signals rather than monthly reports
- API and export for finance systems
Who is this for?
- Teams that want daily visibility into spend without manually checking billing portals.
- Buyers replacing spreadsheets and fragmented native dashboards with one monitoring workflow.
- Operators who need read-only setup, alerts, and forecasting before overrun becomes month-end reality.
Evaluation checklist
- 01
Start a trial
Open a StackSpend workspace with no credit card required.
- 02
Connect your stack
Bring in the providers or cost data you want to evaluate inside StackSpend.
- 03
Review the first 90 days
Check history, alerts, anomalies, and forecast so you can decide whether the workflow is worth adopting.
How does StackSpend support this workflow?
Native tools provide provider-specific reporting and controls. StackSpend adds a shared monitoring workflow across connected sources.
Manual showback decks and finance spreadsheets
- Compiled monthly, so feedback arrives long after the decision
- Built by hand, so they are expensive enough to skip when busy
- No agreed treatment of shared or unallocated spend
- No alerting — a team only learns it overspent at the review
StackSpend
- Per-team views updated daily, not compiled monthly
- Per-team budgets and alerts so showback has consequences
- Unallocated remainder reported explicitly as a readiness gate
- Same data exports to finance when you move to chargeback
What do you get when you connect?
- Setup time
- Fast self-serve setup with no sales cycle required.
- Access model
- Read-only credentials only. StackSpend does not modify provider resources or billing settings.
- Signals
- Daily Slack or email updates, anomaly alerts, and budget tracking in one workflow.
- History and forecast
- Historical spend context plus pace-to-forecast so overruns are visible before month-end.
Check the details before connecting.
Review connection permissions
Read the provider setup guides before sharing credentials.
Provider setup guidesSee the security details
How credentials, tenant isolation and data handling work.
Security and data handlingTalk to the team
Ask about your stack or requirements before connecting.
Contact StackSpendAbout Andrew DayShowback vs Chargeback for Cloud & AI Spend, answered
When is this workflow useful?
- A central budget absorbs every team's overrun so no team changes behaviour
- Chargeback is introduced before tagging coverage is trustworthy and stalls in disputes
- Shared cluster and shared AI key costs have no agreed owner
- The monthly showback deck arrives weeks after the decisions it describes
How does StackSpend handle Showback vs Chargeback for Cloud & AI Spend?
Showback shows each team what it spent without moving money; chargeback bills that cost back to the team's own budget. Almost every company between 20 and 200 people should start with showback, because it creates the feedback loop — the engineer who made the decision sees the consequence — without the internal accounting overhead. Chargeback only pays off once allocation coverage is high and trusted; run it on incomplete tagging and teams spend more time disputing the split than reducing the spend. StackSpend supports showback directly through tag-based allocation, per-team views, and per-team budgets.
What is the difference between showback and chargeback?
Showback shows each team what it spent without moving money; chargeback bills that cost back to the team's own budget. Showback creates the feedback loop — the engineer who made the decision sees the consequence — without internal accounting overhead. Chargeback adds financial consequence but only works once allocation coverage is high and trusted.
Should a 20–200 person company use chargeback?
Usually not at first. Chargeback requires allocation everyone believes, and at that size shared infrastructure and shared AI keys mean a meaningful share of spend has no single obvious owner. Run showback with per-team budgets first; if the unallocated remainder is small and uncontested, chargeback becomes a reasonable next step. Introduced early, it mostly generates disputes about the split.
How do you handle shared infrastructure in a chargeback model?
Either leave shared spend in a central bucket that nobody is charged for and manage it as its own line, or split it by an agreed proxy such as usage share or headcount. The important part is agreeing the treatment before the first invoice, because retrofitting it after a team disputes their number is where chargeback programmes stall.
For the current provider catalogue, see supported integrations.
Tomorrow morning: one number, in Slack.
Connect your providers today and follow spend, budgets and alerts in one place. Review provider permissions before connecting.