Confluent and Aiven costs by cluster and team
Import Confluent Cloud and Aiven billing and allocate streaming and managed database costs to teams.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
A shared cluster's cost or throughput mix changes.
Context used
Remembered
Costory investigates
01
Connect
Confluent Cloud billing and the Aiven Billing API.
02
Put in context
Throughput per service on each shared cluster shows which services drive the cost, before the split.
03
Break down
By cluster, environment and service.
04
Allocate
Usage-based splits for shared clusters.
05
Report
Per-team streaming costs.
Where you see it
Claude
You decide
Data platform validates the split.
Why it matters
Kafka clusters and managed databases are shared by design. Their cost is rarely split.
Who it’s for
Data platform teams, platform engineers
Where it runs
Claude · Slack
What you get
What lands in front of your team
Streaming costs, owned
By team.
Cluster-level detail
Where the spend goes.
Next to cloud
One cost model.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
FAQ
Questions about this playbook
Which platforms are supported?
Snowflake, BigQuery, Datadog, Confluent, Aiven, Elastic Cloud, ClickHouse, Cloudflare and more, plus any FOCUS-formatted billing data in BigQuery.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
A shared service's cost grows, or a new team starts using it.
Split shared infrastructure costs by actual usage
Allocate shared databases, networking and platform services to the teams that use them, based on real usage metrics.
See the playbook
Costory notices
A Datadog product line grows faster than usual.
Datadog spend by product and team
Import Datadog usage and billing estimates, then allocate observability spend to the teams generating it.
See the playbook
Costory notices
Every week, across every connected provider.
One showback across AWS, Google Cloud, Azure, AI and data platforms
Teams see all their costs in one place, whatever the provider: cloud, Kubernetes, data platforms and LLM APIs.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud