Use Cases
Product-ready analytics pages, not feature fragments
Start from your existing backend contracts, add type-safe analytics, and grow from internal use to external APIs without rewriting core logic.
Adoption path
Incremental
Source of truth
Typed queries
Runtime model
In-process or HTTP
Use Cases
Pick the pattern that matches your architecture
Internal Product APIs
Add analytics to existing product endpoints
Keep your route contracts stable and compose analytics directly inside business handlers.
- No forced service split
- Reuse query definitions in-process and over HTTP
- Roll out incrementally by endpoint
Explore use case
Multi-tenant SaaS
Ship tenant-aware analytics APIs by default
Resolve auth context once, inject tenant filters automatically, and enforce role checks in query definitions.
- Tenant isolation without custom middleware sprawl
- Role checks live next to query logic
- Scales from early-stage to enterprise tenancy models
Explore use case
Step 01
Model metrics once
Define analytics in TypeScript with explicit inputs, outputs, and auth expectations.
Step 02
Integrate into your backend
Mount generated routes where needed or call queries in-process from existing handlers.
Step 03
Expand usage safely
Reuse the same definitions across dashboards, services, and internal tools without drift.
Next step
Start with the use case closest to your current architecture
Both paths share the same core model: define once, run anywhere, govern centrally.