Put AI compute
on a budget.
Outlay maps every AI dollar to the ticket, team, and person that drove it — so you can forecast it, budget it, and stop the spend that isn't work. Prompts and keys never leave your environment.
SESSIONS 3 · claude-sonnet 82% · haiku 18%
FIDELITY session — joined on branch + PR metadata, no prompt read
SESSIONS 2 · claude-sonnet 100%
FIDELITY session
BUDGET $24k for the quarter · pace on track
FIDELITY ticket → epic rollup
ALERT pace warning fired JUN 18 · email + webhook to #eng-spend
NEXT hard cap available per program (Controls)
ACTION stopped by team policy · no prompt was read
FIDELITY metadata only — categories, counts, dollars
FIX a one-line task tag in your agent launcher or CI makes it attributable
Four products. One statement.
Connect the tracker and AI tools you already use — read-only, no app rewrite. Each product answers one question a finance leader actually asks.
Every dollar finds its ticket.
Outlay Ledger resolves each AI call to the ticket, epic, and person behind it — from branch, PR, and session metadata. Prompt content is never read, and what can't be attributed says so: unknown, never guessed.
Inside the Ledger →Price the quarter before you build it.
Outlay Forecast prices your open backlog the way you estimate effort — back-tested on your own closed tickets, with the error and sample size always shown. Never a vendor benchmark.
How accuracy is measured →Budgets that act, not just alert.
Outlay Controls holds teams, programs, and epics to a budget: pace-based alerts before overspend lands, an opt-in hard cap that blocks or routes down — and non-work usage stopped per team, without reading a single prompt.
See governance →Buy compute efficiently.
Outlay Procure computes the most efficient mix of flat seats and API credits from real per-person spend — who belongs on a seat, who belongs on credits. Drag your team size and watch the mix reprice.
Inside Procure →Built to pass yours.
Most spend tools see everything you send. Outlay is built so sensitive data physically can't reach us — attribution runs on metadata: task categories, token counts, ticket IDs, dollar figures.
SSO/SAML & SCIM · phishing-resistant passkeys + MFA · full audit log with SIEM export · configurable retention & self-serve erasure · WCAG 2.1 AA · read the security overview
Your AI bill,
itemized.
Start read-only: connect one tracker and your AI usage, and see your real spend itemized in days.
Become a customer →How does Outlay attribute spend to a ticket?
It resolves the work context of each AI call from the most reliable signal available — an explicit task tag from your agent launcher or CI, the git branch, the PR's closing-issue link, or a commit trailer — and maps it to the ticket, epic, and roadmap in Jira, Linear, or GitHub. Where teams already link work to tickets it's automatic; where they don't, a one-line tag makes it reliable, even for remote/CI agents.
Do you see my prompts or my customers' data?
No. Outlay connects with read-only tokens and reads metadata — task category, token counts, ticket IDs, and your provider's usage data. Prompt content, model outputs, and your API keys never reach our servers. That's an architecture, not a policy.
Are budgets hard caps, or just alerts?
Your choice, per program. By default they're pace-based projections that flag a scope trending over — Outlay never touches your traffic. For a true hard cap, the opt-in gateway blocks or routes over-budget calls down to a cheaper model. It fails open: our downtime can never block your traffic, only a budget you set being exceeded can.
How accurate is the forecast?
We back-test it on your own closed tickets — hide one, predict it from the rest, compare to what it actually cost — and show you the measured error and sample size by work type. As more work closes, the number sharpens. We never quote a vendor benchmark.