K99 admin console
The /k99 super-admin dashboard for tenant management, telemetry, and platform health.
Overview
The K99 console at /k99 is the cross-tenant super-admin surface used by Katura's platform team. Tenants do not see it; tenant admins should never need to. It exists for one reason: to keep the lights on for every store running on K99 from a single pane of glass.
Who can access
Access is gated by the requireK99Admin() server guard. Only users with the K99_ADMIN role on a special platform-tenant can reach /k99/*routes. The role cannot be granted through the regular admin UI — it is provisioned directly in the database by Katura engineering.
What you can do from the console
- Tenant directory — every store, plan, MRR, last-seen-active timestamp, and current health.
- Impersonation — securely sign in as any tenant admin for support; every impersonated session is audit-logged.
- Telemetry — request volume, error rates, p95 latency, AI token spend, and Stripe webhook health per tenant.
- Billing — view subscriptions, invoices, dunning state, and trigger refunds or comps.
- Feature flags — turn experimental features on for a tenant or a cohort.
- Migrations & jobs — kick off and monitor long-running platform jobs (CAD re-index, search re-embed, etc.).
Warning
Every action in /k99 is permanently logged with the actor, target tenant, IP, and a structured payload. The audit log is append-only and cannot be edited or deleted, including by K99 admins.
Incident flow
- An alert fires (Sentry, Vercel, custom telemetry).
- Console highlights affected tenants on the home dashboard.
- An operator triages, can impersonate to reproduce, applies a fix, and posts a status update.
- If the incident is tenant-visible, a banner is automatically shown in the affected admin UIs until the incident is closed.