Outlay attributes every dollar of LLM and coding-agent spend to the work you already plan — tickets, epics, roadmap — forecasts the quarter, and lets you enforce a budget per program. Read-only to start; your prompts and keys never leave your environment.
Read-only · metadata-only · BYOK · no app rewrite
Bring your own keys to your AI provider and your tracker (Jira / Linear / GitHub). Outlay reads usage metadata only — token counts and dollar figures. Prompts, outputs, and keys never leave your environment.
Every dollar of LLM and coding-agent spend is mapped to the ticket, team, and person that drove it — then Outlay forecasts the quarter and prices your open backlog, with accuracy back-tested on your own closed work.
Set budgets and hard program caps across teams, get route-down recommendations to cheaper models where they're provably good enough, and enforce before you overspend — not at month-end.
Outlay prices every token class separately — cache reads bill at ~1/10th. Naive trackers that count raw tokens overstate cache-heavy agentic spend several times over.
We don't ask you to trust a vendor benchmark. The forecast is back-tested leave-one-out on your own closed tickets, and we always show the measured error.
Every fidelity tier is shown so the total ties out to your provider's billed figure. A number business can take to the board.
Built metadata-only and read-only. No prompts, outputs, or API keys ever leave your environment.