Three capabilities, fourteen features — each marked with its status and a note on where it was proven or what it still lacks, so you know what works today before you apply.
Each feature says what it does, then its status. Status as of 2026-10-15, the same as on /evidence.
01
Understand and reduce spend
Find the costs worth investigating.
Compare periods and inspect spend by service, account, region or team. Review cost movements with the period and billing basis in view. Checked against the detailed bill (CUR) for June 2026, our own totals landed within ~1% of CUR on our own estate, window-aligned. On yours the same check gives a result once your Cost and Usage Report is connected and imported. The production CUR import ran again on 27 September 2026. September’s CUR, through the 26th, agrees with Cost Explorer to the cent; August’s is $17.07 short and under investigation, so the June 2026 check remains the last clean one.
Connect spend to teams, products and cost centers. Keep configured, inferred and unknown assignments visible for showback and the next cost conversation.
Review idle-resource and capacity findings with their evidence, risk and effort. Give each next step an owner; projected savings remain estimates.
Explore coverage, utilization and commitment scenarios. Compare terms, scope, obligations and uncovered usage before considering a purchase.
02
Choose the right architecture
Put the design behind the spend in view.
Compare supported cloud services and machine types against workload requirements. Review compatibility and operational trade-offs, priced at each cloud's baseline region, instead of assuming a direct replacement.
Review each rightsizing finding beside the utilisation it rests on and the rollback it would need.
Design findings and network cost for an AWS estate, each with its evidence and missing inputs.
Resources by account, region and network at list price, with what it cannot see listed. Swept nightly: Azure subscriptions and Google Cloud projects in full, AWS accounts in their billed regions, up to 20.
A reference design for a new workload, priced on all three clouds from dated list prices.
03
Plan for growth
Understand the economics of what grows next.
Follow instrumented usage by model, feature or tenant. Review token and GPU cost context, pricing assumptions and missing inputs.
Drop a usage export from your AI provider and see what it costs at list price. The file is read in your browser and never uploaded.
Compare actuals with budgets, inspect forecast assumptions and share scoped reports. Keep the reporting period, source coverage and export basis visible.
Cluster and workload usage with its cost basis: the bill for EKS with the CUR import, otherwise list price.
A cost per unit only where a matching denominator exists, never an invented one.
Beta. A status changes only when we have the evidence for it. Architecture and savings scenarios are estimates until your bill confirms them.
One sample estate, four views
The same estate, all the way down.
Overview, Cost Explorer, architecture context and the engineering review all read one fictional ledger, so every number on this page adds up with every other. The walkthrough estate. The live demo is a different fictional estate — three clouds and 90 days of history — with its own numbers.
Sample estate · a fictional company on AWS billing, Sep 1 – 14 · every figure adds up to the cent
2 / 4 · swipe
The thread: +$4,420 in 14 days → 84% of it is checkout‑api → a +$620/day step since Sep 9 → $18,600/mo at stake, projected
Sample estateFictional company · AWS billing · 14-day window
Sample·Illustrative product view — not customer data
CloudJaegerSearch ⌘K
Overview
Explore›
Optimize›
Architecture›
Kubernetes
AI & GPU›
Allocate›
Plan›
Anomalies
Reports›
Settings›
Getting started · Support · Status · TrustDemo viewerRead-only · fictional estate
Explore ›Cost ExplorerDemo workspace · a fictional estate, read-only Run this on your estateExit demoUpdated 4 hours agoExportShare
CloudJaeger
Cost Explorer
Accounts
Regions
Cost Explorer
Where the money went, by any dimensionSep 1 – 14 vs Aug 18 – 31 · by service tag · billed
Window Sep 1 – 14
Compare Prior 14 days
Cloud AWS · 1
Group by Tag · service
Basis Billed · all charges
Through Sep 14 · 4 h ago
checkout‑api explains 84% of the change; three service tags explain all of it.
Where the change came from
change vs prior 14 days · USD · zero-centred
checkout‑api+$3,720
analytics‑warehouse+$1,060
No service tag+$42
web‑edge+$14
orders‑db$0
search‑cluster−$28
event‑bus−$28
log‑archive−$360
−$1k$0+$1k+$2k+$3k+$4k
Bars start at $0 and are drawn to scale; a flat group is shown as $0, never hidden. Same rows as the table below.
Sample estate spend by service tag, Sep 1 – 14 against Aug 18 – 31, USD. The total row equals the window total.
Service tag
Team
Provider
Aug 18 – 31
Change
% change2
Share
checkout‑apiECS Fargate · 2 AZs
Payments1
AWS
$12,460
$16,180
▲ +$3,720
+29.9%
27.4%
No service tag314 AWS services · Lambda, SQS +12
No owner tag
AWS
$11,480
$11,522
▲ +$42
+0.4%
19.5%
analytics‑warehousePostgreSQL on EC2 · cross-AZ transfer
Data Platform
AWS
$9,940
$11,000
▲ +$1,060
+10.7%
18.6%
search‑clusterOpenSearch
Catalog
AWS
$6,720
$6,692
▼ −$28
−0.4%
11.3%
web‑edgeCloudFront
Platform
AWS
$5,180
$5,194
▲ +$14
+0.3%
8.8%
log‑archiveS3 · lifecycle policy
Platform
AWS
$4,760
$4,400
▼ −$360
−7.6%
7.5%
event‑busMSK
Data Platform
AWS
$3,640
$3,612
▼ −$28
−0.8%
6.1%
orders‑dbRDS PostgreSQL · Multi-AZ
Payments
AWS
$420
$420
■ $0
0.0%
0.7%
Total · all spend21 AWS services · rows sum to the window total
AWS
$54,600
$59,020
▲ +$4,420
+8.1%
100.0%
Showing 8 rows · 7 service tags + untagged · 21 AWS services · sorted by Sep 1 – 14 spendBasis: billed · all charges · USD · rows sum to the total · bars scaled to the largest row
checkout‑api$16,180
Payments · AWS · ECS Fargate1▲ +$3,720
27.4%2+29.9% · was $12,460
No service tag3$11,522
No owner tag · AWS · 14 AWS services▲ +$42
19.5%+0.4% · was $11,480
analytics‑warehouse$11,000
Data Platform · AWS · EC2▲ +$1,060
18.6%+10.7% · was $9,940
search‑cluster$6,692
Catalog · AWS · OpenSearch▼ −$28
11.3%−0.4% · was $6,720
web‑edge$5,194
Platform · AWS · CloudFront▲ +$14
8.8%+0.3% · was $5,180
log‑archive$4,400
Platform · AWS · S3▼ −$360
7.5%−7.6% · was $4,760
event‑bus$3,612
Data Platform · AWS · MSK▼ −$28
6.1%−0.8% · was $3,640
orders‑db$420
Payments · AWS · RDS■ $0
0.7%0.0% · was $420
Total · all spend$59,020
21 AWS services · rows sum to the total▲ +$4,420
100.0%+8.1% · was $54,600
1Who owns it: Payments, from the team tag — checkout‑api is +$3,720 of the +$4,420.
2What stands out: +29.9% on one service, +10.7% and −7.6% on the other two that moved, and under 1% on the 5 other rows.
3How we know: grouped by the service tag on each resource; untagged spend keeps its own row, never spread, and the total row equals the headline.
Open the live demo — a fictional estate on three clouds, with nothing to install.
