Evidence
What works today, and how we know.
Every feature this site mentions, with its status as of 15 October 2026, where it was proven, and what it cannot do yet. The statuses start from our feature register of 25 September 2026, checked again against the code on 15 October 2026.
The full register, including the features we will not ship in v1, is shared with design partners. Status mapping: works → Live · works in part → Preview · sample estate only → Demo-only · broken or after v1 → Planned.
Cost visibility · 7
| Feature | Status | Where it was proven | What it cannot do yet |
|---|---|---|---|
| Spend overview | Live | our own AWS estate · totals match the database to the cent · Azure and Google Cloud in Preview | “Last 30 days” is computed more than one way across pages. |
| Cost Explorer | Live | our own AWS estate · Azure and Google Cloud in Preview | The default window can end on a day that is not billed yet. |
| Ownership & allocation | Preview | allocation math proven on Cost Explorer data | Regenerating an issued showback statement replaces it. |
| Budgets, forecasts & reporting | Preview | pacing and forecast agree to the cent · budget alerts not firing yet | Scoped budget alerts do not fire yet. |
| Anomaly detection | Preview | runs nightly in production | The money at stake can show as more than one amount across pages. |
| Alerts — Slack, Teams, email, PagerDuty | Preview | per-sync spend and anomaly alerts, once a workspace owner switches delivery on | Budget alerts, cost monitors and scheduled digests do not run yet. |
| Reports | Preview | downloads work · the monthly review is correct | Scheduled delivery is off, so the weekly digest and scheduled reports are not sent yet. |
Optimisation · 4
| Feature | Status | Where it was proven | What it cannot do yet |
|---|---|---|---|
| Idle & waste cleanup | Preview | real AWS inventory · unpriced items say “not calculable”, never $0 | The cleanup plan checks one AWS region per scan, and prices it at us-east-1 list rates. |
| Rightsizing with evidence | Preview | CPU-based · AWS, Azure and Google Cloud VMs | Azure and Google Cloud VMs are sized on live CPU alone, without memory. |
| Waste & action review | Preview | no saving bill-graded yet | Overlapping actions on one resource can be summed into one total; no saving is bill-graded yet. |
| Commitments & planning | Preview | AWS, Azure reservations, Google Cloud CUDs · no purchasing | Purchases are blocked; recommendations refresh on a button press. |
Architecture · 4
| Feature | Status | Where it was proven | What it cannot do yet |
|---|---|---|---|
| Service & workload alternatives | Preview | most Google Cloud machine types listed, not priced | Some pairs are matched too loosely, such as x86 to Arm. |
| Architecture review | Preview | AWS estates only | Catches too few of the planted defects it is tested on, and checks AWS only. |
| Topology & inventory | Preview | network boxes and links on AWS only | Azure and Google Cloud resources are drawn without network grouping, links or per-resource cost. |
| Design Studio | Preview | dated list prices · some regions unpriced | Two engines give different answers. |
AI and Kubernetes spend · 3
| Feature | Status | Where it was proven | What it cannot do yet |
|---|---|---|---|
| AI & LLM cost analysis | Preview | SDK / OTel push · AI price book 2026-10-v1 | AI spend already on the cloud bill (Bedrock, Vertex AI) shows as a separate, unattributed line. |
| Free AI cost audit | Preview | runs in your browser · AI price book 2026-10-v1 | Prices at list rates from the AI price book, and names what it could not price. |
| Kubernetes workload economics | Preview | lab cluster only · AKS and GKE unpriced | AKS and GKE costs are not priced yet; the bill-backed rung needs the CUR import. |
Connections and platform · 9
| Feature | Status | Where it was proven | What it cannot do yet |
|---|---|---|---|
| AWS | Live | real bills on our own accounts · several-account organisations in testing | Re-running the wizard can create a duplicate connection. |
| Microsoft Azure | Preview | real cost and inventory sync · not yet checked against a real bill | One subscription per connection; no EA, MCA or management-group scope. |
| Google Cloud | Preview | real cost and inventory sync · not yet checked against a real bill | Every new connection uses a service account key; keyless is not offered yet. |
| CUR import | Preview | imported again on 27 September 2026 | 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. |
| FOCUS or CUR file upload | Preview | single-file totals are exact | Use one file per workspace for now; deleting an upload is not built yet. |
| REST API | Live | the OpenAPI document matches the routes | Keys do not expire or rotate yet. |
| MCP server | Preview | key-based answers agree to the cent with the web app | OAuth for third-party clients does not work yet. |
| Public demo | Preview | a read-only sandbox · writes are refused | Some calculators refuse to run in the demo. |
| Sign-in, MFA and sessions | Preview | MFA, idle and absolute session limits, a password re-check for sensitive actions | Some sign-in edge cases are still open. |
Questions
Before you connect an account
What access does CloudJaeger require?
On AWS, a read-only IAM role — we publish the exact policy before you connect, rendered from the CloudFormation template we actually deploy, and you can delete it any time. For an AWS connection we hold the role ARN and a per-connection external id, never a key; on Azure and Google Cloud we hold the read-only credential you issue us, encrypted — the service principal's client secret, or the service account's JSON key.
Will CloudJaeger change my infrastructure?
No. This build has no execution path: nothing is applied to your cloud, with or without an approval. The two modes that would touch your cloud are locked, and live purchases are hard-blocked in code. Findings leave as reports, not as changes. Filing findings as Jira tickets is Planned, not in v1: that path was proven only against our own Jira sandbox.
Does anything run inside my workloads?
No. Nothing of ours runs in your account or on your workloads: we assume a read-only role and call read APIs. A Kubernetes agent exists — a Helm chart you would install and control yourself, which reads your own Prometheus and never calls the Kubernetes API — and it is in Preview: it has been proven only on a lab cluster.
Which clouds are supported?
AWS, through a native read-only connection, is the deepest today. Azure and GCP are in preview: their cost and inventory syncs run on real connections, and no real Azure or GCP bill has been checked against its invoice yet. Oracle Cloud and on-premises arrive through the open FOCUS import path; there is no native connector for either.
What data does CloudJaeger store — and can I take it back?
Read-only cost and usage data: your billing exports plus what the read-only role can describe. Data is encrypted in transit and at rest; no payment card is stored. Export it any time as CSV or JSON, or delete the workspace, which is a documented, real erasure. An export in FOCUS — the FinOps Foundation's vendor-neutral format — exists too, in Preview: its Azure and Google Cloud rows carry no resource id.
What does “verified” mean for a saving?
That your bill moved. Savings stay projected until your invoice actually shows the drop; the word verified is reachable through exactly one code path, and only when the bill isolated the resource that changed. In production that path cannot run today: it counts only changes CloudJaeger opened as a pull request, and no GitHub App is configured.
How is this different from my cloud provider’s own tools?
It builds on them. The providers’ own tools are genuinely good at what they cover — Cost Optimization Hub, Compute Optimizer and Trusted Advisor (and Azure Advisor, GCP Recommender) produce solid rightsizing, idle and commitment recommendations for their own cloud, free and already in your console. CloudJaeger imports those recommendations, deduped, then adds what they don’t carry: ownership, architecture context, one estate across clouds, evidence and confidence, and a savings ledger that keeps every saving projected until a bill shows the drop.
What happens after the pilot or the design partner programme?
The pilot ends either way with the report. Continuing is a conversation, not an auto-renewal — there is no card on file and nothing charges by itself. If you leave, your data exports and the workspace deletes.
Check any row yourself on the sample estate.
Open the live demo — no signupApply for a design partner slot