Five products. The depth behind each.
The same five products you meet on the home page — Ledger, Forecast, Controls, Procure, Route — and the engineering under each: how Outlay costs agentic AI correctly, prices planned work, enforces budgets, buys compute efficiently, and routes every request to the cheapest model that's good enough. Plus the platform layer that takes it all anywhere.
The same usage, costed two ways.
Agentic coding re-sends a large cached prefix every turn, so cache-read tokens — billed at roughly a tenth of base input — dominate the count. Price every token at the base rate, the way most spend tools and spreadsheets do, and the number balloons. We costed our own Claude Code usage both ways.
Measured on our own build sessions:
98% of input-side tokens were cache reads, so the naive method overstates by 7.4×.
Reproduce it yourself: python -m outlay.dogfood --proof-only.
Estimate a project's AI cost before you build it.
Roadmap and sprint planning shouldn't guess at compute. Hand Outlay the planned work — epics and tickets with their requirements and design docs — and it prices each one against the cost model it learned from your own delivered work, with a confidence range you can budget against.
Illustrative. Each item priced from your own per-work-type history; thin-scope items get a wider band, not a false-precise number.
From line item to control plane.
Group teams and projects into programs with one budget. By default Controls is read-only — pace-based alerts (ok → warn → over) fire before a program lands over. Flip on the opt-in gateway and a hard cap blocks or routes over-budget work down automatically. It fails open: our downtime can never block your traffic — only a budget you set being exceeded can.
Platform crossed its cap — 1,240 calls routed down to a cheaper model this month, no work blocked.
The most efficient mix of seats and API credits.
Per-person spend shows who belongs on a flat vendor seat and who belongs on API credits. Procure computes the most efficient split from your real usage — plus commitment sizing and a renewal pack you take to the vendor. It's the analysis nobody buying blind can run. Coming soon.
Illustrative — save $21.5k/mo, shown with its assumptions. In the app, Procure runs on your real per-person spend.
Route every request to the cheapest model that's good enough.
Route scores each request and sends it to the least-expensive model that clears your quality bar — with automatic fallback when a cheaper model would miss it. You keep the output quality and cut the model bill, and you're billed only on the savings Route actually realizes. Coming soon.
Illustrative — save $25k/mo with quality held at your bar. In the app, Route measures realized savings on your own traffic.
The platform layer.
What every product shares: the connectors, the accuracy proof, and the privacy architecture.
Works with your stack
Jira, Linear, GitHub Issues; Claude Code, Cursor, the API — across Anthropic, AWS Bedrock, Google Vertex, and OpenAI / Azure. Reliable attribution even for remote / CI agents via explicit task-tagging.
Accuracy you can check
Every forecast is back-tested on your own closed tickets, leave-one-out — we show the measured error and the sample size, by work type. No vendor benchmark to take on faith.
Privacy by architecture
Every product runs on metadata — connected with read-only tokens. Prompt content, model outputs, and your API key never leave your environment.
It's your spend data — take it anywhere.
Outlay is a hub, not a silo. Export FOCUS-aligned cost rows for any FinOps/BI tool, pull them programmatically through a read-only API, and stream your audit log to your SIEM — all reconciled to the provider invoice, to the cent. No lock-in, ever.
FOCUS-aligned export
Per-ticket charge rows using the FinOps Open Cost & Usage Spec column names — load straight into any FOCUS-aware FinOps or BI tool.
# spec column names · per-ticket rows
BilledCost,ServiceCategory,Tags{team,work_type}
BI & warehouse API
A token-authed, rate-limited endpoint returns your latest report as JSON for any warehouse or BI pipeline — the same attributed numbers as the console.
GET /api/v1/spend
→ { total_usd, rows[], data_quality }
Audit log → your SIEM
Stream every security event to Splunk, Datadog, or S3 — poll the audit API with a cursor for gap-free ingestion, or export CSV for GRC.
GET /api/v1/audit?since=cursor
Plus HMAC-signed webhooks for budget & anomaly events (retried, with a delivery log), and a printable month-end close pack — emailed automatically with the FOCUS CSV attached.
Works with every model and every tool in your stack.
Outlay reads spend from every major provider and connects it to the systems where the work actually happens — read-only, no app rewrite, no prompts leaving your environment.
- Anthropic API + admin usage
- OpenAI
- Azure OpenAI
- AWS Bedrock
- Google Gemini native token accounting
- Google Vertex
- Claude Code session transcripts
- Cursor admin usage
- CI / remote agents task-tagging
- GitHub issues + PRs
- Jira
- Linear
- FOCUS CSV export
- BI / warehouse API
- SIEM audit-log export
- Webhooks
Reconciles against your provider invoice — Anthropic, AWS Cost Explorer, GCP Cloud Billing, OpenAI Costs — so business trusts the number, not a token estimate. Become a customer →
See it on your own spend.
Connect read-only in minutes — your real AI spend mapped to work, costed correctly, forecast, and yours to export.
Read-only to start · prompts never leave your environment · no app rewrite