Who's actually using BharatRouter — active developers, the adoption tail to chase, and what each dev leans on. ← Back to dashboard
Distinct active developers per IST day (left) and adoption % of members (right) — the trend the live dashboard lacks.
Distinct developers with BR-routed traffic each IST day.
Which models the org leans on. By requests — no Finance access needed.
Active developers per workspace. Membership is key-based (api_keys.workspace_id), not HR org.
Ranked by usage. Click a row to see that developer's model mix.
Members with zero BR-routed traffic in this window — the adoption tail to chase.
Adoption = which org members have BR-routed traffic (IST day boundaries). BR is a gateway — no code-output or shadow-AI metrics. Spend tiles need the cost:org:view Finance capability; the whole page needs usage:org:view (own card otherwise).