NearSync Developer Docs

NearSync is a multi-tenant business platform — CRM, Finance, HRMS, Communications, Projects, and AI in one system. These docs are for developers and AI agents building on it: the public API, the MCP server, integrations, and the concepts you need to integrate cleanly.

Looking to use the product (not build on it)? That's the in-app help and the NearSync Academy — this site is the technical reference.

Start here

• Authentication — API keys, OAuth, scopes, and org isolation. Read this first.
• API Reference — the read-only REST surface at https://api.nearsync.tech/v1.
• MCP Server — connect Claude/ChatGPT/Gemini to your org's data at https://api.nearsync.tech/mcp.
• Integrations — Stripe, QuickBooks, HubSpot, Slack, Google/Microsoft, and more.
• BYOK Setup — run the platform against your own Supabase project.

How it's built (the parts that affect you)

Single codebase, runtime-configured. Every tenant runs the same application; behavior is driven at runtime by a system_manifest (modules, feature flags, branding, limits). See Manifest-driven gating.

Two deployment models:

• Managed — your org shares NearSync's Supabase, isolated by org_id + Row-Level Security.
• BYOK — the same code runs against your Supabase project, in the region you choose.

Multi-tenant by org_id + RLS end to end — the same boundary the API and MCP enforce. See Multi-tenancy and Security.

Surfaces

Surface	URL	For
Public API	api.nearsync.tech/v1	read-only REST over your org's data
MCP server	api.nearsync.tech/mcp	AI agents (Claude, ChatGPT, Gemini)
Admin app	app.nearsync.tech	the product UI
These docs	docs.nearsync.ai	developer reference

Tech stack

Layer	Technology
Frontend	React, TypeScript, Vite, Tailwind
Backend	Supabase (PostgreSQL, Auth, Storage, Edge Functions, Realtime)
API / MCP	Supabase edge functions behind api.nearsync.tech
AI	Google Gemini + additional providers via routing
Deployment	Vercel (Git-driven)
Monitoring	Sentry