Welcome to Costory

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, Elastic Cloud, Snowflake, and more. Costory normalizes it so you can explore, explain, and report without building your own data pipeline. In the first hour, you can also connect Costory MCP to Claude or Cursor and start investigating costs from chat.

​

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 Cost Reports so each team gets the right view on a schedule.
• Stop guessing why spend moved. Correlate costs with deploys, incidents, and provider events in Explorer, then add Events and Unit Economics.
• Stop starting every investigation from a blank dashboard. Connect Costory MCP to Claude or Cursor, ask the first cost questions in chat, and save the useful views for dashboards.
• Stop untangling the same tags in every console. Use 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, Elastic Cloud, OpenAI, MongoDB, Confluent Cloud. Explore everything in one 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.

​

Ask Claude or Cursor to investigate

Costory MCP connects your Costory workspace to Claude, Cursor, VS Code, and other MCP-compatible assistants. Once billing data is connected, you can ask questions such as “what changed this week?”, “which services should I group by?”, or “prepare a dashboard for the data team.” Use the assistant to compare periods, find saved views, create alerts, send Cost Reports, and build the cost views that become dashboard widgets.

​

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

​

Start here

Costory starts with a 14-day free trial. Pricing uses a flat fee, so your subscription stays predictable as your cloud bill changes. See Costory pricing. For security and platform reviewers: Costory runs on Google Cloud Platform (GCP) with encryption in transit and at rest. Billing connections use read-only access to your exports or APIs. Review Security, Subprocessors, and SSO and access control.

​

Week one

​

When you need more