Cost control
Per-team cost visibility, metered billing, real-time burn rate.
Live spend per team, user, and repo. Burn rate and projected month-end on the dashboard. Seat limits cap how many seats a team can spend on. Metered billing via Stripe with idempotent set-action - no double charges, no end-of-month surprises. Configurable $-budget caps hard-stop on breach.
Spend MTD
$7,554
76% of budget
Projected
$9,930
↑ 99% of budget
Per seat / day
$3.84
28 active seats
How it works
1
Usage metered per session
Tokens in/out, model, duration captured at session close.
2
Aggregated per scope
Rolled up by team, user, repo, and model in real time.
3
Seen on the dashboard
Live burn rate, projected spend, and seat counts - with soft alerts as spend trends up.
4
Billed via Stripe
Idempotent set-action - exact usage, no double charges.
Deep dives
Real-time burn rate
See overshoot trajectory days before the invoice. The dashboard projects month-end spend from the rolling 7-day burn rate.
Seat limits and $-budget caps
Seat limits cap concurrent paid seats per team, configurable $-budget caps (monthly / weekly / daily) hard-stop on breach, and the dashboard shows live spend per team, user, and repo.
Metered billing accuracy
Stripe set-action with idempotency keys means a replayed event never charges twice. Reconciliation report monthly.
Budget policy
config · budget.yaml
budgets:
- scope: team
target: platform
monthly_cap_usd: 3000
alert_at: [0.8, 0.95]
on_breach: hard_stop
override_requires: role:admin + reason
- scope: user
target: eng-bot
weekly_cap_usd: 500
on_breach: notify
- scope: repo
target: acme-api
daily_cap_usd: 200
on_breach: warn_only
Spend data is per-tenant isolated.
Teams see only their own. Admins see everything. Row-level security in Postgres makes the wrong query impossible, not just discouraged.
Compare
| Synaptyx | Anthropic invoice EOM | Manual tracking | |
|---|---|---|---|
| Real-time | live burn rate | monthly | whenever you check |
| Per-team / per-repo | 3 scopes | org only | if you keep notes |
| Seat limits | per-team caps | no | no |
| Projected month-end | rolling 7-day | surprise | guess |
| Audit log CSV export | one click | PDF invoice | your spreadsheet |
FAQ
Anthropic's published per-model token rates × tokens used, plus a small Synaptyx platform fee for managed plans. Self-host customers see Anthropic-rate-only pricing.
Today: full visibility. The dashboard shows live burn rate and projected month-end so you can act before the invoice. Seat limits cap how many paid seats a team can use. Configurable $-budget caps that hard-stop on breach are enforced today - set per scope and period. Notify-only and warn-only modes are on the roadmap.
Yes - seat limits are set per team today, and configurable $-budget caps per scope (company / team / user / repo) and period (day / week / month), with audited admin overrides, are enforced too.
Managed customers are billed via Synaptyx's Stripe. Self-host customers can connect their own Stripe account or skip billing entirely (BYOK to Anthropic).
Ready to govern your AI infrastructure?
Request access in minutes - or talk to us about your air-gap deployment.