Turn
into
The shift
Dashboards got cheap.
Context didn't
Costory is the context layer between your bills and your agents. Allocation, normalization and correlation, so the next prompt answers why, not just what.
What it is
The missing cost context layer
for engineering and finance
01
Turn Claude, Codex, or Cursor into a FinOps practitioner
Costory hands your AI assistant the context that lives in your infra engineer's head: billing data correlated with Datadog usage, GitHub deploys, pricing changes, and traffic patterns.
02
Get explained,
not just described
Claude can build a 'what changed' dashboard in minutes. The why is the hard part: deploys, pricing shifts, traffic, business metrics. Costory brings that context.
03
Your AI assistant doesn't just answer,
it acts
Use Costory's tools to create a saved view, set a budget alert, log a cost event, send a weekly digest to Slack. All from the same conversation.
04
The same context for the agents your team is deploying
Your deploy, scaling, and ops agents are starting to touch cost-sensitive infra. They pull the same allocated spend, budget headroom, and baselines your engineers use, through the same endpoint.
Distribution
Infra cost context flows everywhere your teams work
Legacy FinOps makes you log into their dashboard. Costory pushes cost context into the tools your teams already use.
Slack
Automated reports by team, alerts, and digests delivered in-channel.
MCP
Claude Desktop, Claude Code, Cursor, VS Code, Dust, and any MCP-compatible client.
BI dashboards
PowerBI, Looker, Data Studio. Finance and leadership see the same numbers in the tools they already report from.
Developer platforms
Backstage and internal IDPs. Engineers see their service's cost next to the rest of its metadata, without switching tools.
Web app
Dashboards, explorer, configuration, and the embedded MCP client with interactive charts.
Raw data vs context
Raw billing data vs
the cost context layer
Native cloud MCPs, CUR exports, and Cost Explorer give your AI assistant raw numbers. Costory gives it context.
In practice
What asking Costory looks like
When you ask
"Why did costs spike for the data team last week?"
Costory returns a cost diff, likely drivers, related deploys and metrics, historical baseline, and suggests the next drill-down.
When your agent asks
"Before scaling the inference cluster, show the ML team's current compute trend and remaining budget headroom."
Costory returns allocated costs by team, historical trend, and budget status. It contextualizes: historical spend, trend, comparable past events, remaining budget.
AUDIENCES
For every team that touches cost decisions
Testimonials
Trusted by Eng teams who
don't have time for spreadsheets
Alternatives
Four ways to solve cost visibility
How it works
From connection to conversation in minutes
1/ Connect
Add your providers via Terraform or Cloudformation: AWS, GCP, Azure, Datadog, OpenAI, Anthropic, and more.
2/ Map
Costory auto-suggests allocations from your existing tags and metadata: teams, products, environments, business units.
3/ Distribute
Use Cloud & LLM cost data everywhere: Slack digests and alerts, BI tools, internal developer platforms. Every team lead sees their costs without asking anyone.
4/ Ask
When a report raises a question, dive deeper: query Costory through your AI assistant or jump into the web app.
Pricing
Pay for the context layer,
not the dashboards.
Most popular
Know what changed, who's responsible, and what to do about it.
€
EUR
/ month
Billed Annualy
No percentage of cloud spend
No enterprise sales call
No need to hire a FinOps team
FAQ