Cost at a glance
Auto-filled from when tracking started. Per-day and per-month figures derive from it. Total and per-tester are live from the server.
Where the money goes
AeroDataBox quota
Set these to your current AeroDataBox plan (you moved to Ultra on 7/7). AeroDataBox meters in units, and different endpoints cost different amounts, so this bar is approximate. Values persist in this browser; the provider dashboard is the source of truth.
External API spend (estimated)
| Provider | Calls | $/call | Est. cost |
|---|---|---|---|
| Total external | – | – |
Estimates for at-a-glance visibility. Each provider's own dashboard is the source of truth.
Claude spend by feature
| Feature | Calls | $/call | Cost |
|---|---|---|---|
| Total Claude | – | – |
Claude spend by model
| Model | Calls | Cost |
|---|
Feature adoption
| Feature | Testers | % | Uses |
|---|
Cost forecast — project a future month
Projects total cost as flat infrastructure + AeroDataBox quota steps + a small true-variable cost per user (– / user / month). Flight tracking is a flat AeroDataBox subscription that steps up only when you cross your plan's unit quota (set above), so cost grows in steps, not linearly, and projected cost per user falls as you scale.
Real users often use the app less than hands-on testers. Below 1.0 = lighter; above = heavier.
–
Projected total cost · next month
| If next month has… | Cost / user | Projected monthly cost |
|---|
Fixed monthly costs (flat, don't scale with users)
Flat platform costs that don't scale with users. Editable. AeroDataBox is handled in the forecast above as a quota step, so it's not listed here. Per-user uses the forecast user count above.
| Cost | $ / month | Per user |
|---|---|---|
| Total fixed / month | – | – |
Margin model — usage cap & in-app top-up
Live data (testers, costs, adoption) comes from /api/telemetry/summary. Forecast, fixed costs, and the margin model are computed in your browser from that live run rate plus the inputs you set. Nothing here is saved server-side.