Profile and personalization
User profile, medical context, preferences, access state, and consent-aware context for app and API use.
Platform
The operating system behind Transit surfaces.
Transit connects product UI, API access, integrations, and agent workflows through one backend shape so health context stays consistent across every surface.
NetlifyServerless product APIs and integration flows.
SupabaseAuth, storage, and canonical relational data.
MCPOAuth-backed machine access path.
Canonical domains
Transit is organized around reusable health domains, not disconnected provider silos.
Signals and records
Biomarkers, wearable sync, food meals, interventions, symptoms, sleep, training, and recovery flags.
Artifacts and actions
Weekly briefs, narratives, companion actions, agent runs, and shared artifacts.
Architecture
The platform keeps frontend decisions close to backend contracts.
Netlify Functions
Authenticated product APIs, billing flows, MCP transport, integration sync, and companion runtime endpoints.
Supabase
Canonical data model, auth foundation, migrations, and row-level access boundaries.
Shared clients
Typed API clients and runtime modules centralize fetch behavior, error surfaces, and endpoint contracts.