# Costory > Costory is a FinOps agent for cloud, AI and data spend. It ingests billing data from AWS, Google Cloud, Azure, Kubernetes, Snowflake, Datadog, OpenAI, Anthropic and other providers, allocates it to teams, products and environments, and explains cost changes alongside deploys and usage metrics. It works in Slack and, through a hosted FinOps MCP server, in Claude, Claude Code, Cursor, GitHub Copilot, Dust and other assistants. Access to your cloud is read-only (billing and usage exports; no write access). Data is hosted in the EU. Pricing is published: Copilot €250/month and Copilot Pro €1,000/month, both billed annually, with a 30-day free trial. Costory does not buy Reserved Instances or Savings Plans and does not apply automated rightsizing. Comparison pages state the date their claims about other tools were last checked; those claims come from each vendor's public documentation and pricing pages. Costory is the publisher of this site. ## About - [About Costory for AI and LLMs](https://www.costory.io/ai-info): Structured facts: what Costory is, who it is for, pricing, integrations, MCP tools, what it does not do, FAQ. Last reviewed October 2026. - [About Costory](https://www.costory.io/about): Company page: Costory SAS, Paris. - [How Costory works](https://www.costory.io/product): Costory allocates cloud, Kubernetes, data and AI bills, adds deploys, owners and usage metrics, and runs a FinOps agent that monitors and follows up. ## Product - [FinOps MCP](https://www.costory.io/finops-mcp): Costory's hosted FinOps MCP gives Claude, Cursor, GitHub Copilot and Dust allocated cost across clouds, Kubernetes and LLM APIs, plus deploys. EU-hosted. - [Costory for Slack](https://www.costory.io/slack): The Costory agent works in your Slack channels: anomaly threads with the likely cause and owner, budget alerts, weekly showback per team, answers in any thread. - [AI assistants that work with the Costory MCP](https://www.costory.io/assistants): Hub page for the assistant guides below. - [Costory in Claude](https://www.costory.io/assistants/claude): Use the Costory MCP from Claude to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Claude Code](https://www.costory.io/assistants/claude-code): Use the Costory MCP from Claude Code to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Cursor](https://www.costory.io/assistants/cursor): Use the Costory MCP from Cursor to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in GitHub Copilot](https://www.costory.io/assistants/github-copilot): Use the Costory MCP from GitHub Copilot to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in ChatGPT](https://www.costory.io/assistants/chatgpt): Use the Costory MCP from ChatGPT to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Codex](https://www.costory.io/assistants/codex): Use the Costory MCP from Codex to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Gemini CLI](https://www.costory.io/assistants/gemini-cli): Use the Costory MCP from Gemini CLI to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Grok Bot](https://www.costory.io/assistants/grok-bot): Use the Costory MCP from Grok Bot to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Dust](https://www.costory.io/assistants/dust): Use the Costory MCP from Dust to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Costory in Windsurf](https://www.costory.io/assistants/windsurf): Use the Costory MCP from Windsurf to query allocated AWS, GCP, Azure, Kubernetes and LLM cost, and to set alerts and reports. - [Connect guides](https://www.costory.io/connect): Guides to connect Claude, Claude Code, Cursor and GitHub Copilot to AWS, Google Cloud, Azure, Kubernetes, Snowflake, Datadog and LLM spend via the Costory MCP. ## Pricing - [Pricing](https://www.costory.io/pricing): Copilot €250/month (up to €10M annual cloud spend) and Copilot Pro €1,000/month (up to €20M annual cloud spend), billed annually; 30-day free trial; available through AWS and Google Cloud Marketplace. Above €20M annual cloud spend, contact Costory. ## Comparisons - [All comparisons](https://www.costory.io/compare): Costory compared with the AWS, Azure and Google Cloud MCP servers and with Vantage, CloudZero, Finout and Kubecost. Claims checked October 2026. - [FinOps tools in 2026: how to choose by need](https://www.costory.io/best-finops-tools-2026): Twelve FinOps tools compared by fit, pricing model, assistant support and limits, with sources. Costory is our product. Last updated 15 October 2026. - [AWS Billing MCP vs Costory](https://www.costory.io/compare/aws-billing-mcp-vs-costory): AWS's free Billing and Cost Management MCP runs locally on your AWS credentials and covers AWS only; when it is enough and when a hosted layer across providers is useful. - [Google Cloud Billing MCP vs Costory](https://www.costory.io/compare/google-cloud-billing-mcp-vs-costory): Google's official Cloud Billing MCP manages billing accounts, IAM and SKU prices but returns no spend data; how to ask an assistant about GCP spend. - [Azure Cost Management MCP vs Costory](https://www.costory.io/compare/azure-cost-management-mcp-vs-costory): Microsoft's Azure MCP server adds Cost Management and Pricing toolsets; what it covers and where Azure-only coverage stops. - [Costory vs AWS Cost Explorer and spreadsheets](https://www.costory.io/compare/cost-explorer): Costory vs AWS Cost Explorer and spreadsheets: when Cost Explorer is enough, and when automated reporting and explained changes across providers help. - [Costory vs asking ChatGPT or a DIY MCP](https://www.costory.io/compare/chatgpt): Costory vs asking ChatGPT or a DIY MCP: when a DIY setup works, and why normalized, allocated data and FinOps tools give consistent answers. - [Costory vs legacy FinOps platforms](https://www.costory.io/compare/legacy-tools): Costory vs legacy FinOps platforms: built for engineering teams without a FinOps department. Flat pricing, connected in under 30 minutes. - [Vantage vs Costory](https://www.costory.io/compare/costory-vs-vantage): Vantage's published plans compared with Costory's flat pricing, 30-day free trial and Slack, Claude and Cursor access, as of October 2026. - [CloudZero vs Costory](https://www.costory.io/compare/costory-vs-cloudzero): CloudZero vs Costory: unit cost focus, MCP access model, pricing (quote vs published flat), setup time. When each is the right pick. - [Finout vs Costory](https://www.costory.io/compare/costory-vs-finout): Finout's MCP is hosted and read-only; Costory's can create alerts, reports and dashboards. Coverage, pricing and fit compared. - [Datadog Cloud Cost Management vs Costory](https://www.costory.io/compare/costory-vs-datadog-cloud-cost-management): Datadog CCM puts cost next to observability; Costory adds cloud, data and LLM providers and an MCP built for cost questions. Where each fits. - [Kubecost vs Costory](https://www.costory.io/compare/costory-vs-kubecost): Kubecost (IBM) allocates in-cluster cost; Costory ingests Kubecost or OpenCost exports and adds cloud, data and LLM cost. When you need one or both. - [nOps vs Costory](https://www.costory.io/compare/costory-vs-nops): nOps focuses on AWS commitment management and savings; Costory on allocation and context for engineers and their assistants. Which problem you are solving. - [DoiT vs Costory](https://www.costory.io/compare/costory-vs-doit): DoiT bundles cloud resale, support and FinOps tooling; Costory is a flat-priced context layer you buy with a card. How the models differ. - [IBM Cloudability vs Costory](https://www.costory.io/compare/costory-vs-cloudability): Cloudability is built for a central FinOps team; Costory for platform engineers and their assistants. Setup, pricing model and fit compared. - [CloudHealth vs Costory](https://www.costory.io/compare/costory-vs-cloudhealth): CloudHealth (Broadcom) vs Costory: governance-heavy FinOps suite vs an MCP-first cost context layer. Who each is for. ### Alternatives - [Alternatives to popular FinOps tools](https://www.costory.io/alternatives): Looking for an alternative to Vantage, CloudZero, Finout, Kubecost or AWS Cost Explorer? Options compared by fit, with claims checked October 2026. - [Vantage alternatives in 2026](https://www.costory.io/compare/alternative-vantage): Options compared by use case (MCP access, pricing model, setup time), including when to stay on Vantage. Costory is one of the listed options and the publisher of the page. - [CloudZero alternatives in 2026](https://www.costory.io/compare/alternative-cloudzero): Options compared by use case (MCP access, pricing model, setup time), including when to stay on CloudZero. Costory is one of the listed options and the publisher of the page. - [Finout alternatives in 2026](https://www.costory.io/compare/alternative-finout): Options compared by use case (MCP access, pricing model, setup time), including when to stay on Finout. Costory is one of the listed options and the publisher of the page. - [Kubecost alternatives in 2026](https://www.costory.io/compare/alternative-kubecost): Options compared by use case (MCP access, pricing model, setup time), including when to stay on Kubecost. Costory is one of the listed options and the publisher of the page. - [AWS Cost Explorer alternatives in 2026](https://www.costory.io/compare/alternative-aws-cost-explorer): Options compared by use case (MCP access, pricing model, setup time), including when to stay on AWS Cost Explorer. Costory is one of the listed options and the publisher of the page. - [CloudHealth alternatives in 2026](https://www.costory.io/compare/alternative-cloudhealth): Options compared by use case (MCP access, pricing model, setup time), including when to stay on CloudHealth. Costory is one of the listed options and the publisher of the page. - [Cloudability alternatives in 2026](https://www.costory.io/compare/alternative-cloudability): Options compared by use case (MCP access, pricing model, setup time), including when to stay on Cloudability. Costory is one of the listed options and the publisher of the page. - [DoiT alternatives in 2026](https://www.costory.io/compare/alternative-doit): Options compared by use case (MCP access, pricing model, setup time), including when to stay on DoiT. Costory is one of the listed options and the publisher of the page. - [nOps alternatives in 2026](https://www.costory.io/compare/alternative-nops): Options compared by use case (MCP access, pricing model, setup time), including when to stay on nOps. Costory is one of the listed options and the publisher of the page. - [Ternary alternatives in 2026](https://www.costory.io/compare/alternative-ternary): Options compared by use case (MCP access, pricing model, setup time), including when to stay on Ternary. Costory is one of the listed options and the publisher of the page. ## Use cases - [All use cases (playbooks)](https://www.costory.io/use-cases): FinOps playbooks the Costory agent runs for you: allocation and showback, optimization, anomaly investigation, unit economics, budgets, finance close, AI spend. ### Allocation and showback - [Allocate cloud costs without perfect tagging](https://www.costory.io/use-cases/cost-allocation-without-perfect-tagging): Map accounts, projects, resource names and partial tags to teams with rules, instead of waiting for a tagging project to finish. - [One showback across AWS, Google Cloud, Azure, AI and data platforms](https://www.costory.io/use-cases/multi-cloud-showback): Teams see all their costs in one place, whatever the provider: cloud, Kubernetes, data platforms and LLM APIs. - [Split shared infrastructure costs by actual usage](https://www.costory.io/use-cases/shared-cost-allocation): Allocate shared databases, networking and platform services to the teams that use them, based on real usage metrics. - [Fill owner columns from a lookup file kept in git](https://www.costory.io/use-cases/cost-enrichment-tagging): Map namespaces, accounts or feature keys to teams with an enrichment file (beta), then report on the new columns in Explorer, dashboards, alerts and reports. - [Split shared API costs across teams with usage data](https://www.costory.io/use-cases/shared-api-cost-split): Allocate untagged or shared API costs, like a single LLM key or a shared data platform account, to teams based on actual usage. - [Split production and non-production costs automatically](https://www.costory.io/use-cases/automated-environment-allocation): Allocate every cost line to prod, staging, dev or sandbox using account names, projects, clusters and labels. - [Tag coverage audit: the agent finds allocation gaps and drafts the rules](https://www.costory.io/use-cases/tag-coverage-audit): Find which label keys could become dimensions, how much spend each one covers, and where untagged cost is concentrated. - [Kubernetes cost allocation by namespace, team and workload](https://www.costory.io/use-cases/kubernetes-cost-allocation): Break EKS, GKE and AKS costs down by cluster, namespace and workload, and roll them up to teams. - [Dynamic cost reallocation for EKS using Datadog usage](https://www.costory.io/use-cases/eks-usage-based-reallocation): Split shared EKS cluster costs across teams in proportion to what each team's workloads actually use, measured in Datadog. - [Stable team costs with contracted cost](https://www.costory.io/use-cases/contracted-vs-billed-cost): Give teams a usage-driven cost view that doesn't swing when Savings Plan discounts are shared across accounts. - [Weekly showback per team, posted in each team's Slack channel](https://www.costory.io/use-cases/team-cost-reports): Every engineering team gets its own weekly cost report in its own Slack channel, scoped to the services it owns. ### AI and LLM spend - [LLM cost allocation by team, feature and customer](https://www.costory.io/use-cases/llm-cost-allocation): Allocate model spend from OpenAI, Anthropic, Azure OpenAI, Bedrock, Vertex AI and OpenRouter to teams, features and customers. - [All AI spend in one view: OpenAI, Anthropic, Bedrock, Vertex AI and more](https://www.costory.io/use-cases/ai-spend-overview): The agent tracks total AI spend across model APIs, cloud AI services and AI tools, and reports the weekly trend in one place. - [Cost per AI feature: tokens, GPUs and infrastructure in one number](https://www.costory.io/use-cases/cost-per-ai-feature): Combine model API spend with the GPU and serving infrastructure behind each AI feature, then divide by usage for a true cost per request. - [Choose LLM models and routing based on cost per feature](https://www.costory.io/use-cases/llm-model-routing): The agent tracks per-model spend for each AI feature across OpenAI, Anthropic, Bedrock and Vertex AI. - [Cursor and Claude Code spend per developer](https://www.costory.io/use-cases/ai-coding-spend-per-developer): Track AI coding tool spend per user and per model, from Cursor and the Anthropic Claude Code connector, next to the rest of your cloud. - [claude.ai Enterprise cost per user](https://www.costory.io/use-cases/claude-enterprise-cost-per-user): Import per-user Claude Enterprise cost with an Analytics API key, and allocate seats and usage to teams. - [Track generative media spend: ElevenLabs, Kling AI and BytePlus](https://www.costory.io/use-cases/genai-media-costs): Import voice, video and media generation spend next to cloud and LLM costs, and allocate it to products. ### Anomalies and investigation - [Investigate a cost spike and find the deploy behind it](https://www.costory.io/use-cases/cost-spike-investigation): When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window. - [Investigate anomalies in a Slack thread with the FinOps agent](https://www.costory.io/use-cases/slack-anomaly-threads): When an alert fires in #finops or a team channel, reply in the thread and the FinOps agent investigates: which team, which service, which deploy. - [Cost impact of every deploy, from GitHub events](https://www.costory.io/use-cases/deploy-cost-impact): Capture deploys, PR merges and releases from GitHub or your CI/CD pipeline, and see which ones changed cost. - [Add the cost of an incident to your postmortem](https://www.costory.io/use-cases/incident-cost-postmortem): Incidents are logged as events. After each one, the agent reports what it cost: retries, autoscaling, failover traffic and extra LLM calls. - [Backtest a cost alert before it goes live](https://www.costory.io/use-cases/backtested-cost-alerts): Preview how often an alert would have fired over the past weeks before turning it on, so alerts stay rare and useful. - [Route cost alerts to the owning team's channel](https://www.costory.io/use-cases/route-alerts-to-owners): Each team gets its own alerts in its own Slack or Teams channel, scoped to the services it owns. - [Catch SKU price changes and marketplace renewals](https://www.costory.io/use-cases/provider-price-changes): Provider events flag SKU price changes and marketplace renewals on the timeline, so unexplained increases get explained. ### Optimization - [Rightsizing recommendations grounded in real usage](https://www.costory.io/use-cases/rightsizing-with-usage-context): The agent compares what you pay for compute with what services actually use in CloudWatch or Datadog. - [Find over-requested Kubernetes workloads and right-size requests](https://www.costory.io/use-cases/kubernetes-overprovisioning): Measure the gap between requested and available CPU and memory, convert it to cost, and get request changes per deployment. - [Find unattached volumes, underused disks and growing backups](https://www.costory.io/use-cases/idle-resources-cleanup): Surface storage waste and idle resources by owner, so each team gets a short cleanup list with the cost of doing nothing. - [Storage class and tiering recommendations for S3 and Cloud Storage](https://www.costory.io/use-cases/storage-tiering): Find buckets in expensive storage classes, check access patterns, and get lifecycle and tiering suggestions per owner. - [Understand cross-AZ and egress costs, then reduce them](https://www.costory.io/use-cases/network-egress-costs): The agent breaks down data transfer by provider, service, account and team, flags jumps and points to the architecture choices behind them. - [Find candidates for newer instance generations and Graviton](https://www.costory.io/use-cases/graviton-and-generation-upgrades): Use the compute metadata in your billing data to list older instance families by owner and estimate the impact of upgrading. - [Snowflake warehouse review: sizing, idle time and expensive queries](https://www.costory.io/use-cases/snowflake-warehouse-optimization): Use warehouse and query history from Snowflake account usage to find oversized warehouses, idle credits and the queries that cost the most. - [A weekly optimization shortlist posted to each team's channel](https://www.costory.io/use-cases/weekly-optimization-shortlist): Every Monday, each team gets three optimization candidates for its own services, with evidence, in its Slack channel. - [Measure the impact of every optimization you ship](https://www.costory.io/use-cases/measure-optimization-impact): Log each optimization as an event and compare cost before and after, so the team can show what each change saved. ### Commitments and credits - [Savings Plans and Reserved Instances coverage review](https://www.costory.io/use-cases/savings-plan-coverage): The agent watches covered versus uncovered spend and utilization. - [Committed Use Discount planning for Google Cloud](https://www.costory.io/use-cases/gcp-cud-planning): Import CUD metadata, see coverage per project and team, and size spend-based commitments on your steady baseline. - [Track Savings Plan and RI purchases, expirations and renewals](https://www.costory.io/use-cases/commitment-expiry-tracking): Provider events put commitment purchases, marketplace renewals and SKU price changes on the cost timeline, so nothing expires silently. - [Track cloud credits and runway](https://www.costory.io/use-cases/credits-runway): Follow credits received and consumed per provider and estimate when they run out, so the switch to paid usage is planned. ### Unit economics - [Track cost per customer, per request or per active user](https://www.costory.io/use-cases/unit-economics): Combine allocated cloud cost with your business and usage metrics to build unit costs that leadership can track over time. - [Cost per tenant for multi-tenant SaaS](https://www.costory.io/use-cases/cost-per-tenant): Allocate shared infrastructure to tenants using labels, namespaces or usage metrics, and track infrastructure cost per client. - [Cost per API request with Datadog or CloudWatch metrics](https://www.costory.io/use-cases/cost-per-api-request): Divide a service's allocated cost by its request volume from Datadog or CloudWatch, and track it release after release. - [Cost per thousand active users with Amplitude](https://www.costory.io/use-cases/cost-per-active-user): Correlate cloud cost with Amplitude active users and track cost per thousand MAU or WAU. - [Cloud COGS and gross margin by product line](https://www.costory.io/use-cases/gross-margin-by-product): Allocate infrastructure to product lines and combine it with revenue from a sheet or warehouse table to track COGS and margin. - [Show the right cost metric to each persona](https://www.costory.io/use-cases/persona-cost-metrics): Finance, engineering and leadership each get the cost metric that fits their decisions: billed, contracted or unit cost. - [Price bursty workloads with hourly cost granularity](https://www.costory.io/use-cases/hourly-cost-granularity): Use hourly cost data to measure bursty jobs, price each event or batch, and connect optimization work to per-event cost. ### Budgets, reporting and finance - [Team budgets with forecast-based alerts](https://www.costory.io/use-cases/budget-alerts): Monthly budgets per team, with Slack or email alerts when actual spend or the end-of-month forecast crosses a threshold. - [Monthly budget vs actual review with engineering leads](https://www.costory.io/use-cases/budget-vs-actual-review): A ready-made dashboard and monthly report with target, actual, forecast and delta per team, for the VP Infrastructure review. - [Build next year's cloud budget from allocated history](https://www.costory.io/use-cases/annual-budget-planning): Start budget season from 12 months of allocated cost per team, growth trends and known changes, with every version tracked. - [End-of-month cost forecast per team, before the invoice](https://www.costory.io/use-cases/end-of-month-forecast): See where each team will land at month end, based on a forecast model, and investigate drifts while there's still time. - [Automate the monthly cloud cost review](https://www.costory.io/use-cases/monthly-cost-reporting): A monthly report with an executive summary, root causes and trends, generated from a Cost digest and delivered automatically. - [Weekly cost digest: the changes that matter, ranked by impact](https://www.costory.io/use-cases/weekly-cost-digest): Every significant cost shift ranked by impact, with an AI summary, delivered to Slack, Teams or email. - [A board and exec cost pack in minutes](https://www.costory.io/use-cases/exec-cost-pack): Total spend trend, top drivers, budget progress, unit costs and month-over-month comparison in one executive view. - [Monthly chargeback pack by cost center, ready for finance](https://www.costory.io/use-cases/chargeback-pack): A monthly, frozen view of allocated cost per cost center, exported to BigQuery or shared as a PDF for finance. - [Month-end close: allocated cloud costs ready for finance](https://www.costory.io/use-cases/month-end-close): Use Costory's frozen month-end numbers, allocated to cost centers, as the cloud input to your close. - [Cloud cost accruals from month-to-date data](https://www.costory.io/use-cases/cloud-cost-accruals): Estimate the month's cloud cost for accruals using month-to-date data and forecasts per cost center. - [Report cloud costs in EUR across USD invoices](https://www.costory.io/use-cases/eur-reporting): Report in your company currency while providers bill in USD, with consistent conversion rules across AWS, Google Cloud, Azure and Datadog. ### Data platforms - [Snowflake cost by warehouse, team and workload](https://www.costory.io/use-cases/snowflake-cost-allocation): Allocate Snowflake credits to teams and workloads using warehouses and query history, next to your cloud bill. - [BigQuery cost by dbt model, package and team](https://www.costory.io/use-cases/bigquery-dbt-cost): Label BigQuery jobs with dbt metadata and allocate processing and storage costs to models, packages and owners. - [Datadog spend by product and team](https://www.costory.io/use-cases/datadog-cost-allocation): Import Datadog usage and billing estimates, then allocate observability spend to the teams generating it. - [Confluent and Aiven costs by cluster and team](https://www.costory.io/use-cases/kafka-cost-allocation): Import Confluent Cloud and Aiven billing and allocate streaming and managed database costs to teams. ### Setup and workflow - [Connect cloud cost reporting in 30 minutes, first report the next day](https://www.costory.io/use-cases/setup-in-30-minutes): Connect AWS, Google Cloud, Azure and Datadog billing with Terraform or CloudFormation, then send your first report. - [Cost context in your terminal with Claude Code](https://www.costory.io/use-cases/cost-questions-in-claude-code): Connect the Costory MCP to Claude Code so the agent checks what a service costs, how it changed and who owns it before you ship a change. - [Cost context in Terraform pull requests](https://www.costory.io/use-cases/terraform-pr-cost-review): Add current cost context for the resources touched by a Terraform pull request. ## Integrations - [Integrations](https://www.costory.io/integrations): Costory ingests cost from AWS, Google Cloud, Azure, Kubernetes, Snowflake, BigQuery, Datadog, OpenAI, Anthropic and more, then allocates it to teams. ### Cloud - [AWS](https://www.costory.io/integrations/aws): Connect AWS to Costory: CUR 2.0 (BCM Data Exports) via CloudFormation or Terraform. - [Google Cloud](https://www.costory.io/integrations/gcp): Connect Google Cloud to Costory: BigQuery billing export with detailed usage (+ CUD metadata). - [Azure](https://www.costory.io/integrations/azure): Connect Azure to Costory: Azure Cost Management exports via Terraform or manual setup. - [Oracle Cloud](https://www.costory.io/integrations/oracle-cloud): Connect Oracle Cloud to Costory: OCI native cost reports (API signing key). - [Scaleway](https://www.costory.io/integrations/scaleway): Connect Scaleway to Costory: Scaleway IAM secret key + Organization ID. - [Cloudflare](https://www.costory.io/integrations/cloudflare): Connect Cloudflare to Costory: Cloudflare PayGo billing (API token). - [FOCUS](https://www.costory.io/integrations/focus): Connect FOCUS to Costory: FOCUS-compliant billing data in BigQuery (custom billing format). ### Kubernetes and data platforms - [Kubernetes](https://www.costory.io/integrations/kubernetes): Connect Kubernetes to Costory: EKS and GKE natively with no agent, AKS and other clusters through a Kubecost or OpenCost export. - [Snowflake](https://www.costory.io/integrations/snowflake): Connect Snowflake to Costory: Snowflake account usage via key-pair authentication. - [BigQuery](https://www.costory.io/integrations/bigquery): Connect BigQuery to Costory: GCP billing export + BigQuery skill/dashboard template. - [ClickHouse Cloud](https://www.costory.io/integrations/clickhouse): Connect ClickHouse Cloud to Costory: ClickHouse Cloud billing. - [Confluent Cloud](https://www.costory.io/integrations/confluent): Connect Confluent Cloud to Costory: Confluent Cloud billing. - [Aiven](https://www.costory.io/integrations/aiven): Connect Aiven to Costory: Aiven Billing API. - [Elastic Cloud](https://www.costory.io/integrations/elastic-cloud): Connect Elastic Cloud to Costory: Elastic Cloud Organization API key. - [Datadog](https://www.costory.io/integrations/datadog): Connect Datadog to Costory: Datadog usage and billing estimates (+ metrics and CI Visibility). ### AI and LLM providers - [OpenAI](https://www.costory.io/integrations/openai): Connect OpenAI to Costory: OpenAI organization costs with a read-only Admin API key. - [Anthropic](https://www.costory.io/integrations/anthropic): Connect Anthropic to Costory: Anthropic Console API usage (Admin API) and claude.ai Enterprise costs. - [Amazon Bedrock](https://www.costory.io/integrations/aws-bedrock): Connect Amazon Bedrock to Costory: AWS CUR 2.0 with caller-identity allocation (line_item_iam_principal). - [Vertex AI](https://www.costory.io/integrations/vertex-ai): Connect Vertex AI to Costory: GCP BigQuery billing export (project isolation or per-call labels). - [Azure OpenAI](https://www.costory.io/integrations/azure-openai): Connect Azure OpenAI to Costory: Azure Cost Management exports (deployments, tags). - [OpenRouter](https://www.costory.io/integrations/openrouter): Connect OpenRouter to Costory: OpenRouter Management API key. - [Cursor (AI coding spend)](https://www.costory.io/integrations/cursor): Connect Cursor (AI coding spend) to Costory: Cursor Admin API key or Terraform. - [ElevenLabs](https://www.costory.io/integrations/elevenlabs): Connect ElevenLabs to Costory: ElevenLabs workspace API key. - [Kling AI](https://www.costory.io/integrations/kling-ai): Connect Kling AI to Costory: Kling AI usage and billing (API). - [BytePlus](https://www.costory.io/integrations/byteplus): Connect BytePlus to Costory: BytePlus billing (Seedance, ModelArk). ### Events and usage metrics - [GitHub](https://www.costory.io/integrations/github): Connect GitHub to Costory: GitHub integration: deploys, PR merges and releases as event markers. - [CI/CD events](https://www.costory.io/integrations/ci-cd-events): Connect CI/CD events to Costory: Events API: post build and deploy events from any CI/CD pipeline. - [AWS CloudWatch](https://www.costory.io/integrations/aws-cloudwatch): Connect AWS CloudWatch to Costory: External metric: CloudWatch read policy and trust policy, queried live. - [GCP Cloud Monitoring](https://www.costory.io/integrations/gcp-cloud-monitoring): Connect Google Cloud Monitoring to Costory as an external metric (Monitoring Viewer, queried live) and see its metrics next to your cloud costs. - [Amplitude](https://www.costory.io/integrations/amplitude): Bring Amplitude usage metrics into Costory: active, new, weekly and monthly active users, queried live, to compute unit costs such as cost per active user. - [Tsuga](https://www.costory.io/integrations/tsuga): Bring Tsuga metrics, log and trace aggregations into Costory with a read-only Operation API key, to compute unit costs and split shared costs by usage. - [Google Sheets](https://www.costory.io/integrations/google-sheets): Bring numeric metrics from a Google spreadsheet into Costory as usage metrics, to compute unit costs and split shared costs by usage. - [Custom metrics](https://www.costory.io/integrations/custom-metrics): Connect Custom metrics to Costory: Custom Metrics Push: hourly metrics over HTTP with an organization API key. ## Security - [Security and data access](https://www.costory.io/security): Costory reads native billing and usage exports. No agents, no code, no write access to your cloud. Role-scoped OAuth MCP, enterprise SSO, EU data residency. ## Docs - [Documentation index (llms.txt)](https://docs.costory.io/llms.txt): Page list for the documentation site, with a one-line description per page. - [Documentation, full text (llms-full.txt)](https://docs.costory.io/llms-full.txt): Full text of the documentation in a single file. - [Documentation home](https://docs.costory.io): Quickstart, billing data setup, usage metrics, events, MCP and Explorer. - [FinOps MCP (docs)](https://docs.costory.io/features/mcp.md): Query AWS, GCP and Azure spend from Claude, Cursor or VS Code; investigate cost spikes, create alerts and send cost reports. - [Quickstart (docs)](https://docs.costory.io/get-started/quickstart.md): Connect AWS, GCP, Azure and Datadog and set up automated Slack and Teams cost reports. ## Blog - [Blog](https://www.costory.io/blog): Practical guides on cloud cost allocation, Kubernetes and AI/LLM spend, and FinOps with Claude, from the Costory team. - [LLM Cost Allocation: How to Attribute Spend on OpenAI, Anthropic, Bedrock, Vertex and Mistral](https://www.costory.io/blog/llm-cost-allocation-vertex-bedrock): How to attribute LLM spend by provider (API keys, projects, IAM roles, labels) and combine it in one view. - [How we built our FinOps MCP server: lessons learned (Jul 16, 2026)](https://www.costory.io/blog/how-we-built-our-finops-mcp-server-lessons-learned): Engineering notes on normalizing billing data from several providers behind one MCP server. - [Cloud Unit Economics: How BeReal calculates the cost of a Single Notification (Aug 26, 2026)](https://www.costory.io/blog/cloud-unit-economics-how-bereal-cost-a-single-notification): Example from BeReal of pricing a single push notification using cost, events and usage metrics. - [Costory on AWS and GCP marketplaces (Jun 17, 2025)](https://www.costory.io/blog/news-costory-available-on-aws-and-google-cloud-marketplaces): Since June 2025, Costory can be purchased through AWS Marketplace and Google Cloud Marketplace. - [Google Cloud Ready - BigQuery (Apr 7, 2025)](https://www.costory.io/blog/costory-google-cloud-ready-bigquery): Costory was recognized as a Google Cloud Ready - BigQuery partner in April 2025. - [Costory on AWS Marketplace](https://www.costory.io/blog/costory-aws-marketplace): Costory is available on AWS Marketplace, so teams can purchase it through their existing AWS billing. ## Optional - [Sitemap](https://www.costory.io/sitemap.xml): All public URLs, including 61 connect guides (assistant-to-provider setup pages). - [Careers](https://www.costory.io/careers): Join Costory in Paris. Open roles in engineering and sales at a small, high-trust team building cost context for engineering teams and their AI assistants. - [Privacy](https://www.costory.io/privacy): Privacy policy. - [Terms](https://www.costory.io/terms): Terms of service. - [MSA](https://www.costory.io/msa): Master services agreement.