Vercel Deployment

NearSync is deployed as three separate applications on Vercel. BYOK clients choose between two deployment models depending on how much infrastructure control they want.

Application Structure

The NearSync platform consists of three independently deployed applications:

Application	Purpose
Admin Dashboard	The primary business operations interface for your team
Client Portal	External-facing portal for your clients
Marketing Website	Public-facing marketing site

Each application is a separate Vercel project pointing to the same monorepo codebase. Turborepo handles build orchestration so that only the affected application rebuilds when changes are made.

Deployment Model 1: NearSync-Managed (Default)

This is the recommended model for most BYOK clients. NearSync handles all deployment infrastructure while your data remains in your own Supabase project.

How It Works

1. NearSync creates three Vercel projects connected to the NearSync platform codebase
2. Your environment variables are configured in each Vercel project, pointing to your Supabase instance
3. When NearSync pushes updates to the main branch, your deployment auto-rebuilds with the latest code
4. You receive updates simultaneously with all other clients
5. No action required from you for routine updates

What NearSync Manages

• Vercel project configuration and build settings
• Code deployments and rollbacks
• Build optimization via Turborepo
• SSL certificates and edge caching

What You Manage

• Your Supabase database (data, backups, scaling)
• Your custom domain DNS records
• Your third-party API keys and integrations

Custom Domains

You point your own domains to the Vercel deployments:

• admin.yourcompany.com for the admin dashboard
• portal.yourcompany.com for the client portal
• yourcompany.com for the marketing site (optional)

DNS configuration is a one-time setup. Vercel automatically provisions and renews SSL certificates for your domains.

Deployment Model 2: Client Self-Hosted (Enterprise)

For organizations that require full control over their deployment infrastructure.

How It Works

1. You receive build artifacts with each NearSync release
2. You deploy to your own infrastructure (Vercel, Netlify, Cloudflare Pages, Docker, or any static hosting platform)
3. You pull updates at your discretion
4. Database migrations are provided as SQL diff files per release (see Schema Migration)

What You Manage

• Deployment platform and configuration
• Build pipeline and CI/CD
• SSL certificates and CDN
• Update timing and rollback decisions
• Your Supabase database
• Your custom domains

Requirements

• The platform is built with Vite and requires Node.js 18+ for building
• The monorepo uses Turborepo for build orchestration
• Each application has its own build command that builds only the relevant app and its dependencies

Software Updates

Update Delivery

Aspect	NearSync-Managed	Self-Hosted
Application code	Automatic on push to main	Build artifacts per release
Database migrations	Applied during maintenance window (advance notice)	SQL diff files you apply manually
Frequency	Continuous delivery	Release-based
Rollback	NearSync handles	You handle

Database Migration Updates

When a release includes database schema changes:

• An incremental SQL diff file is provided covering changes since the previous release
• For NearSync-managed deployments, migrations are applied during a scheduled maintenance window with advance notification
• For self-hosted deployments, you apply the migration via the Supabase Dashboard SQL editor or CLI at your convenience
• Migrations are backward-compatible where possible; breaking changes require coordinated upgrades

Next Steps

• Review data sovereignty guarantees for your deployment
• Understand the security model that protects your data