Skip to main content
If you own infrastructure and get pulled into cost questions, you are in the right place. Costory is built for engineers who ship features and still answer “what changed on the bill?” without a dedicated FinOps team. You might use Costory when:
  • Finance or leadership asks for a monthly breakdown and you would rather not rebuild the same spreadsheet.
  • Spend jumps and you need to know if it was a deploy, usage, or something the provider changed.
  • You want teams to see their own numbers in Slack or Teams without you acting as a human report router.
You connect billing data from AWS, GCP, Azure, Datadog, and more. Costory normalizes it so you can explore, explain, and report without building your own data pipeline.
About “30 minutes”: That timeline assumes you start a trial, connect at least one billing datasource, and route a first notification to Slack, Teams, or email. You need Cloud Billing Admin access on your cloud account, and a Slack or Teams admin if you want those apps installed for alerts. Export lag and daily freshness: see Billing data refresh. See Prerequisites in the Quickstart.Ready to ship? Open the Quickstart and walk through trial, billing, and your first report.
Cost Explorer drill-down across cloud providers

​
What you can stop doing

  • Stop building and babysitting billing ETL just to get a unified view. Connect exports or APIs, and Costory ingests line items without you owning pipelines or schemas. Start with Billing data.
  • Stop running the monthly cost review by hand. Use the Digest to rank what moved and draft explanations. You tune the breakdown tree and share when it matches how your org talks about cost.
  • Stop copy-pasting numbers into Slack or slides. Use Slack Reports (and Teams or email) so each team gets the right view on a schedule.
  • Stop guessing why spend moved. Correlate costs with deploys, incidents, and provider events in Cost Explorer, including events and metrics.
  • Stop untangling the same tags in every console. Use Feature Engineering and Virtual Dimensions to clean labels and map costs to teams or environments.

​
What Costory does

​
See all your cloud costs in one place

Costory pulls billing data from your providers and normalizes it into a single view. No more switching between consoles or stitching exports by hand. AWS, GCP, Azure, Datadog, OpenAI, MongoDB, Confluent Cloud. Explore everything in one Cost Explorer.

​
Understand why costs changed

Costory ties spend movements to causes you already care about: GitHub deploys, Kubernetes signals, incidents, and provider events such as purchases. When your bill moves, you can see whether it tracked a release, a usage spike, or a pricing change.
You always start by ingesting normalized billing into Cost Explorer. Optionally, you connect event sources such as GitHub, CI/CD, or the custom Events API so deploys, releases, and other signals appear as timeline markers. Those markers sit on the same time axis as your cost curves, so you can compare spend with what shipped or changed. See Explore with context: metrics and events and the Events setup guides.

​
Get reports automatically, not manually

The Digest breaks monthly spend into a tree and surfaces ranked changes with draft summaries. You adjust the Cost Breakdown Tree until the story matches your team, then share to Slack, Teams, Notion, or PowerPoint. What used to take half a day to a full week can run on a schedule instead.

​
Your first hour

1

Open the Quickstart

Create your trial and follow the guided path: Quickstart: automated cloud cost reporting in 30 minutes. Check Prerequisites so billing access and collaboration apps are lined up before you start.
2

Connect billing data

Link AWS, GCP, Azure, or other billing datasources. Costory uses read-only access to ingest exports or APIs. You do not manage warehouse schemas or sync jobs.
3

Get your first report out

Route a report to Slack, Teams, or email so your team sees value in the tools they already use.
4

Optional: organize and deepen

When you are ready, clean up labels with Feature Engineering, add Virtual Dimensions, and turn on the Digest for a structured monthly review.

​
Start here

For security and platform reviewers: Costory runs on Google Cloud Platform with encryption in transit and at rest. Billing connections use read-only access to your exports or APIs. Security · Subprocessors.
Users authenticate through Clerk, including OAuth with common identity providers. Customer data retention can be aligned with your policy. How read-only billing access works is described in Billing data.

​
Week one

Quickstart

Trial, billing connection, and first report end to end

Billing data

Providers, ingestion model, and read-only access

Slack Reports

Scheduled cost updates per team channel

​
When you need more

Cost Explorer

Multi-cloud exploration, drill-downs, and event context

Digest

Monthly tree, ranked changes, and draft summaries you refine before sharing

Tags

Merge labels, allocate untagged spend, and split shared costs
Last modified on March 20, 2026