Navrik
Navrik is a multi-tenant business platform: a workspace-scoped back-office (CRM, calendar/booking, commerce, staff, reviews, social) exposed through a first-party API, an MCP server, and an in-portal AI agent. A workspace's own website (storefront, booking, marketing) is a thin front-end; Navrik is the backend and system of record.
Core concepts
- Workspace — the tenant. Every row, key, and setting is scoped to a
workspace_id. Users belong to a workspace via membership; data is isolated by row-level security (RLS). - Operator vs buyer — operators (workspace members) run the business in the Navrik portal (
/app). Buyers are the workspace's end customers; they never log into Navrik — they use the workspace's own site, which calls Navrik's public/token endpoints. - System of record — Navrik owns the authoritative data; external systems (HubSpot, Stripe, Xero, …) are projections via a per-field ownership map. See ADR-0002.
Three ways to use a workspace
- Portal (
/app) — the operator's back-office UI. - REST API (
/api/v1) — programmatic access with ansk_live_key. See API and the live reference. - MCP (
/api/mcp) — the same capabilities as tools for AI clients. See MCP.
Where to go next
- New here? Start with Getting started.
- Building a website on top of Navrik? See Build a storefront.