CostReveal reads the bills of your AI, cloud and API providers, attributes every cost to the team, feature or customer behind it, and shows how sure each figure is. Including the part it cannot explain yet.
7 day free trial. No card, no SDK, no code changes.
CostReveal, HomeExample
October 2026
All projects, in US dollars
Attribution reconciled to the bill
Spend this month
$248,391
Up 8.4 percent from September 2026
Explained
90%
$223,262 with a direct, inferred or allocated basis
Unknown
$25,129
Shown, never spread across teams
Explained 90%
Unknown 10%
By team
Checkout
inferred$79,640
Search
inferred$64,582
Shared platform
allocated$47,620
AI assistant
allocated$31,420
Not yet explained
unknown$25,129
What changed
EC2 up $12,430, 18 percent
$69,056 to $81,486
OpenAI API tokens up $6,820, 19 percent
$35,895 to $42,715
S3 down $1,240, 9 percent
$13,778 to $12,538
Next best action
Tag the untagged EC2 instances in us-east-1 to explain about $25,000 more.
One view across the AI, cloud and APIs you already run.
OpenAI
Anthropic
AWS
Azure
Google Cloud
Oracle Cloud
Kubernetes
Snowflake
Databricks
Datadog
New Relic
Grafana Cloud
Twilio
Cloudflare
Cursor
Stripe
OpenAI
Anthropic
AWS
Azure
Google Cloud
Oracle Cloud
Kubernetes
Snowflake
Databricks
Datadog
New Relic
Grafana Cloud
Twilio
Cloudflare
Cursor
Stripe
OpenAI
Anthropic
AWS
Azure
Google Cloud
Oracle Cloud
Kubernetes
Snowflake
Databricks
Datadog
New Relic
Grafana Cloud
Twilio
Cloudflare
Cursor
Stripe
And any other vendor’s bill, as FOCUS files you upload or send on a schedule.
The problem
The bill tells you what. Not who, and not how sure.
Cost tools report totals with confidence they have not earned. Finance stops trusting the numbers, and engineering stops looking at them.
A cost report today
An invoice total, split by service, with no owner on any line.
Shared costs spread across teams by a rule nobody can see.
Estimates and measurements presented exactly the same way.
The spend nobody can explain quietly folded into someone else.
With CostReveal
Costs attributed to the team, feature or customer behind them, with the evidence for each.
Shared costs split by a rule you can open and inspect.
A basis on every figure, so you know what to rely on.
Unknown shown as Unknown, with the one change that would explain it.
See it work
From an unexplained bill to an owner for every line.
A short walkthrough of how a month of spend becomes cost per team, feature and customer, with the evidence behind each figure.
The product
One place for AI, cloud and API spend, and every answer shows its evidence.
Attribution to the people behind the spend
Every cost lands on the team, feature, service, model, customer or user behind it, from the tags, labels and usage data you already have, and any dimension of your own, such as environment. Group by any of them from one page.
CheckoutPayments teaminferred$79,640
SearchDiscovery teaminferred$64,582
Shared platformSplit at fixed percentagesallocated$47,620
AI assistantDivided by usage dataallocated$31,420
Coverage you can act on
How much spend is explained, and the one change that would explain the most of the rest.
90 percent explained. Tag the untagged EC2 instances in us-east-1 to explain about $25,000 more.
A basis on every figure
Four labels, from measured to unknown. Finance knows what will hold, and engineering knows what to improve.
direct
Measured exactly, from the provider itself.
inferred
A strong existing signal, such as a tag, pointed to it.
allocated
A shared cost split by a rule you can inspect.
unknown
Not yet explained. Shown, never hidden, with what would explain it.
Shared cost, split in the open
A cluster, a database, a support contract: shared costs are allocated by a rule you choose and can inspect, and never folded into one team's number.
Split at fixed percentages$47,620
Checkout$22,858
Search$16,191
AI assistant$8,571
Budgets and alerts
Budgets per project, provider, service, team, feature, customer, user or view, with alerts by email and Slack as spend nears each limit, and cost spikes that name the team, account or workload that drove them, so the people who own it decide what happens next.
AI assistant$31,420 of $35,000
90 percent used. The team was alerted at 80 percent.
How it works
From an invoice total to an owner for every dollar.
Setup connects your billing data, and CostReveal only ever reads it. Everything after it builds on evidence you already produce.
Step 01
Connect your billing data
Each provider through its own billing export or usage API. No SDK, no code changes, and CostReveal only ever reads.
Minutes to connect; first figures within minutes to a day, as each provider reports
Step 02
Attribute with evidence
Costs are matched to teams, features and customers from tags, labels, the owners you name and usage data. Each figure records the signal it came from.
Tags, labels and usage data you already have
Step 03
Close the gap
Coverage shows what is explained and what is not, and the one next step that would explain the most of the rest.
One next best action at a time
Reconciliation
It ties out to the bill. To the cent.
Every period, what CostReveal attributed adds up to the lines the provider billed, and those are checked against the provider's own total wherever it states one. Nothing is added and nothing goes missing.
Every period
Checked when the invoice lands, not once at setup.
Nothing absorbed
A difference is shown and explained, never hidden.
Against the provider
Checked against its own total wherever it offers one.
AWS, September 2026Example
ExplainedDirect, inferred or allocated
$223,262.00
UnknownShown, never spread across teams
$25,129.00
Total in CostReveal
$248,391.00
Invoice from AWS
$248,391.00
Reconciled. Difference $0.00
For every team
Finance, engineering and security, looking at the same evidence.
Numbers that hold at month end
Close the month on figures you can defend in front of the CFO and the auditor.
Spend by cost center, with the basis on every figure
Spend no invoice confirms yet, marked as such until it does
Attribution that adds up to the bill, to the cent, every period
Each organization is separated by PostgreSQL row level security, enforced below the application and verified every time the service starts.
The narrowest access by design
Credentials are read only wherever the provider offers it, and encrypted with AES-256-GCM. Where a provider offers nothing narrower, as with an OpenAI or Anthropic admin key, the setup says so, and CostReveal only ever reads billing and usage with it.
Sign in your way
SAML single sign on, two step verification you can require of everyone, and sessions you can review and end from any device.
An audit trail you cannot turn off
Invitations, access and settings changes are recorded as they happen, with data export and erasure for every person.
Pricing
Fixed plans, monthly or yearly. Never a percentage of your bill.
Start with a free trial on your own spend. Each plan covers your spend up to its limit for one fixed price, so a busy month never changes the bill.
Read access to billing and usage data, through each provider’s own mechanism: a Cost and Usage Report read through a read only role for AWS, a service principal for Azure, a service account for Google Cloud, an Admin API key for OpenAI or Anthropic. AWS access cannot create, change or delete anything. OpenAI and Anthropic do not let an admin key be limited to reading, so CostReveal says so before asking for one, only ever reads with it, and stores it encrypted.
Do we need to install an SDK or change our code?
No. Attribution starts from what you already have: billing exports, resource tags, the owners you name for workspaces, and Kubernetes labels. Where only your application knows which customer or feature a call was for, it can send that as OpenTelemetry usage data, which most applications already export; CostReveal shows how much spend it would explain, and you decide.
How do we know the figures are right?
Every month is checked: the ledger built from your billing lines against the attribution on every dimension, which must agree exactly, and against the provider’s own total wherever the provider offers one. A closed month that differs is shown as a variance, never adjusted silently, and an open month is marked pending until the invoice closes.
What happens to spend that cannot be attributed?
It is shown as Unknown, with its amount and the single change that would explain the most of it. It is never spread across teams to make a report look complete.
How is our data kept separate from other customers?
Each organization is isolated by PostgreSQL row level security, enforced in the database below the application, and verified every time the service starts.
What does it cost?
A 7 day free trial, then Starter at $99, Pro at $299 or Enterprise from $999 a month, per organization. Paid yearly, Starter is $990 and Pro $2,990: two months free. Each plan is a fixed price that covers spend up to its limit, never a percentage of your bill.
Start with your own numbers.
Connect a provider, read only wherever it allows, and see your spend attributed, with the basis on every figure. The first 7 days are free.