For Finance
A reliable cloud and AI number, without chasing engineering
Costory gives you the cloud and LLM bill, allocated by team, product, and cost center, and ready to flow into the BI or planning tool you already report from. No month-end Slack thread with the infra lead, no manual reconciliation, no two-versions-of-the-truth when the board asks.
The status quo
Why finance and engineering never show the same number
AWS, GCP, and Datadog already pipe into BigQuery — but 40% of line items land untagged
OpenAI and Anthropic usage lives in a separate API nobody's wired up
Finance needs the invoiced number — net of savings plans, commitments, and credits
Engineers need the raw number — what their last deploy actually cost, before financial engineering smooths it out
A data engineer rebuilds the allocation model every time pricing, products, or teams change
The data is in the warehouse. The mapping from infrastructure to product, team, and customer isn't — and the same dollar has to show up two ways: the amount finance pays, and the amount engineering caused. One number can't serve both. So eng reads Grafana, finance reads Looker, the board asks "what does this customer cost us?" and the honest answer is a two-week project.
What Costory delivers
The context layer between your cloud bill and your P&L
Allocated the way you report
Mapped to cost centers, product lines, and customer segments. Not raw SKUs, not provider-specific taxonomies but the dimensions you actually use in the P&L.
Flows into the tools you already use
Push allocated data to PowerBI, Looker, BigQuery, or your planning stack (Pigment, Anaplan, NetSuite via export). Your existing month-end workflow keeps working: better numbers, less wrangling, on time.
Three views, one source
The same source, three different numbers
Finance, engineering, and procurement don't need the same number. Costory gives each the view that fits their job, all from the same allocation model.
Finance
The invoiced total after discounts, credits, Savings Plans, and EDP commits are applied, ready for the P&L.
Engineering
List price, before any discounts or credits, so engineers see the cost of what they just shipped and can actually act on it.
Procurement
Marketplace spend, RI and Savings Plan utilization, and EDP progress against contract, so procurement sees how the company is tracking against what it bought.
How it ships
How you get the right numbers, without adding work to engineering
Your infra lead installs a Terraform module once, 30 minutes. Allocation runs on the tags they already maintain. No re-tagging project, no new dashboard to babysit, no recurring ask.
Use cases
Use cases built for finance
Automate budgets
Automated close-of-month readout, context pre-attached.
Monthly reviews
Automated close-of-month readout, context pre-attached.
The right metric for every persona
Finance, CTO, squad lead, same source, different view.
What your exec team wants
The cost view your board and exec meetings actually need.
Unit economics
Cost per customer, per feature, per product line.
Reallocate API costs
Chargeback shared API and platform costs to the consuming teams.
Outcomes
What you get with Costory
Month-end close doesn't wait on the infra team
Cloud numbers tie to engineering's, every time
Budgets and forecasts by team, product, and cost center
Allocated data flows straight into your BI or planning tool, no more FP&A wrangling
Pricing that makes sense to finance
€250 / month flat — up to €10M annual spend
No percentage of cloud spend
No enterprise sales call
Predictable line item in your software budget
FAQ