Snapshot mode. The metrics API is not reachable, so every figure below is the verified snapshot taken on 30 August 2026. This is what you see when opening the file locally. Deploy to Cloudflare Pages with the environment variables set and the same page goes live.
Read the numbers this way. Figures cover all environments, not just production. Mobile traffic still carries environment = development on every event (VDV-235 §C1), so filtering on production would silently show zero iOS and Android users. Internal hosts — localhost and the CS staging server — are excluded. Real scale today is roughly 10–20 daily active users.
Growth
Engagement
Content & community
Navigation
Viraj Copilot
Money
Unit economics — derived from OpenRouter spend ÷ PostHog usage
Read this one carefully. The OpenRouter account is shared, but the viraj key accounts for 145M of 145M tokens in the last 30 days, so effectively all of this spend is Viraj. What it cannot separate is beta riders from your own and CS's development and testing — both run through the same key. So treat the per-user figures as an upper bound on real rider cost, and the total as exact. Splitting them needs per-request app attribution, which is why the COGS fields matter (VDV-235 §A1).
Full monthly cost of one active riderModelled
Mapbox navigation MAU $0.30 + maps MAU $0.004 + 10 trips $0.80 = ≈$1.10
AI, if they use Copilot at the current rate = ≈$22.50
Against Rider Pro at ≈$13.37/month (yearly) or ≈$23.70/month (weekly).
Mapbox is 5–8% of revenue and comfortable. Copilot is the entire subscription.
The three levers, in order of effectRecommendation
1. Record COGS per transaction — VDV-235 §A1. Until this lands every figure on this page is an average, and averages hide the rider costing $200.
2. Cut calls per message — 34 model calls per Copilot message is the agentic loop. Fewer tool round-trips, or a cheaper model for tool selection.
3. Raise the cache hit rate — 28.9% today. A stable system prompt prefix is the usual fix and it is close to free.
Mapbox consumption — hand-entered from the console, 30 Aug 2026
All of these come from Mapbox's API, despite their docs claiming usage data has none. The console's own /billing/usage/v2 carries every billing SKU — including nav3coremau (29) and nav3coreagtrip (28), the two Navigation SDK lines that matter most — and /billing/contracts/pricing-details returns our contracted tier prices rather than the public list. Verified against the console to the digit on 30 Aug 2026. The catch is the credential: both endpoints need billing:read, which Mapbox will not grant to any token this account can create, so the figures are refreshed from an authenticated browser session rather than server-side. If a refresh is missed the page shows the last good numbers with their date, never zeros.
| Service | Usage | Free tier | Headroom | Change | Price after free tier |
|---|
What is working, and where it comes from
Every metric below is live and trustworthy today. "Source" is the system that owns the answer — one system per question, so two dashboards can never disagree.
| Metric | Source | Event / field | Freshness |
|---|
What is missing, why, and who unblocks it
Nothing here is guesswork — each row names the specific blocker and the single action that clears it. Owner is either Burak (access, credentials, a decision) or CS (code). Ticket references are VDV.
| Metric | Status | Why it is blocked | Owner | Action that unblocks it |
|---|