Build your own FinOps tool, or don’t.

One dashboard is free. A shared tool is not.

One engineer with Claude and a billing API gets a useful dashboard in an afternoon. That part is free, and we recommend it. The cost starts when the rest of the engineering team needs to use it too. Teams we talk to spend several weeks building a framework, the tools and an agent harness that others can share. Then they have to host it, maintain it and keep adding features, on top of their platform roadmap.

What a shared internal tool takes

Build (weeks)

Ingestion for each provider (cloud, data cloud, LLMs); normalization and amortization of commitments; cost metrics that finance and engineering agree on; allocation rules with history that survives reorgs; access for the whole team; an agent harness that doesn’t hallucinate numbers.

Run (forever)

Hosting and on-call; schema drift every time a provider changes its billing export; LLM price tables kept up to date; new providers and new teams; alerts tuned so they aren’t noise.

Grow (forever)

Every feature the team asks for next (budgets, unit economics, Slack alerts, reports) lands on the same platform team’s backlog.

Buy (30 minutes)

Connect your billing exports with Terraform in under 30 minutes. Allocation in YAML, unit economics, formula alerts, budgets, Slack, the MCP and the API, for every user. From €3,000 a year, never a % of your bill.

Start 30-day free trial

What you’d build, and what Costory already runs

You’d need

Costory ships

Ingestion per provider, kept up to date with schema changes

20+ billing connectors: clouds, Kubernetes, data clouds, LLM APIs

Commitment amortization, cost metrics finance agrees with

One cost model, the same number for every team

Allocation that survives reorgs

YAML enrichments in git, dated, backfilled

An agent harness that doesn’t invent numbers

Skills plus Scouts, every number traceable to the invoice line

Access for the whole team

Unlimited users, Slack, the MCP

Hosting, on-call

Hosted in the EU, read-only on your cloud

Keep building. Just not the plumbing.

If you were asked to build, you can still build, on top of Costory: your own agents through the MCP, your own dashboards from the BigQuery export, your own automation through the public API and Terraform. Costory is the cost model underneath.

The skills your agents run are open source: fork them and add your own.

name: component_ownership
description: Generated from the service catalog
keyField: component   # the column your component label lands in
#...
targetColumns:
  - name: team
    mode: replace
  - name: cost_center
    mode: replace
entries:
  # a reorg: past costs keep the old owner
  - key: checkout-api
    when: { start: "2025-01-01", end: "2026-03-31" }
    then:
      team: Payments
      cost_center: CC-410
  - key: checkout-api
    when: { start: "2026-04-01" }
    then:
      team: Commerce Platform
      cost_center: CC-520
  # a shared database: each team pays its share of daily query time
  - key: orders-postgres
    then:
      metric:
        integrationId: datadog
        query: sum:postgresql.queries.time{db:orders} by {team,cost_center}
      propagates: [team, cost_center]

Leaving is easy

Your rules are YAML in your git repo. Your allocated cost exports to your warehouse. If you stop using Costory, you keep both.

Start 30-day free trial

From 250€/month, never a % of your bill. 30 days free, no credit card.

Start 30-day free trial

Talk to a human →