Business metrics
Your own metrics next to your cloud costs
Custom Metrics Push: hourly metrics over HTTP with an organization API key
How Costory uses Custom metrics
When a signal only exists in a cron job, a sidecar or a warehouse Costory cannot query, you push it: hourly points sent over HTTP with an organization API key.
Typical uses are a business counter (orders, jobs, active tenants) to get cost per order, a usage key to split shared cost, or a backfill of past hours. Timestamps are truncated to the hour in UTC, and creating the integration needs a Costory admin.
Step by step: Custom metrics setup in the Costory docs.
Questions you can ask
“Show cost per tenant using the usage we push per tenant.”
“What is our cost per 1,000 conversations this month?”
“Split the shared LLM key by requests per service.”
Setup guide: Custom metrics in the Costory docs.
Playbooks
Playbooks that use Custom metrics
What the Costory agent can watch, investigate and report on for you, with this in the loop.
All playbooks
Costory notices
A shared API or platform bill lands without an owner.
Split shared API costs across teams with usage data
Allocate untagged or shared API costs, like a single LLM key or a shared data platform account, to teams based on actual usage.
See the playbook
Costory notices
A bucket keeps growing in an expensive class with little access.
Storage class and tiering recommendations for S3 and Cloud Storage
Find buckets in expensive storage classes, check access patterns, and get lifecycle and tiering suggestions per owner.
See the playbook
Costory notices
A tenant's infrastructure cost grows faster than its plan.
Cost per tenant for multi-tenant SaaS
Allocate shared infrastructure to tenants using labels, namespaces or usage metrics, and track infrastructure cost per client.
See the playbook
Costory notices
A batch run or live event costs more than usual.
Price bursty workloads with hourly cost granularity
Use hourly cost data to measure bursty jobs, price each event or batch, and connect optimization work to per-event cost.
See the playbook
Costory notices
Monthly, or when a feature's unit cost moves.
Cost per AI feature: tokens, GPUs and infrastructure in one number
Combine model API spend with the GPU and serving infrastructure behind each AI feature, then divide by usage for a true cost per request.
See the playbook
Connect in under 30 minutes. Get your first optimization recommendation the next day.
30-day free trial. Copilot, €250/month, or Copilot Pro, €1,000/month, billed annually.
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