Managed vs. BYOK
NearSync supports two deployment models. Both run the same application code - the difference is where your database lives.
Comparison
| Aspect | Managed | BYOK |
|---|---|---|
| Database location | NearSync's Supabase (shared, multi-tenant) | Your own Supabase project (any region) |
| Data isolation | org_id column + RLS policies | Full database isolation |
| NearSync data access | Operational access for support | Metadata-only via Sentinel heartbeat |
| Key ownership | NearSync holds infrastructure keys | You hold all keys |
| Seats | Priced per seat | Unlimited (your infrastructure cost) |
| Backup responsibility | NearSync | You |
| Region selection | NearSync's Supabase region | You choose any Supabase region |
| Infrastructure cost | Included in monthly fee | You pay Supabase directly |
| Compliance scope | NearSync is data processor | NearSync is software licensor only |
| Setup time | Instant (sign up and go) | 1-2 hours (onboarding call) |
When to choose Managed
- You want to evaluate NearSync quickly
- You prefer NearSync to handle infrastructure, backups, and maintenance
- Your data residency requirements are met by NearSync's hosting region
- You want a predictable monthly cost with no infrastructure management
When to choose BYOK
- Data sovereignty is a regulatory requirement
- You need your database in a specific geographic region
- You want full control over backups, access logs, and infrastructure
- Your team size is your own infrastructure cost rather than a per-seat fee
- You need NearSync to have zero access to your business data
Switching between models
Managed to BYOK: NearSync can migrate your data to a new Supabase project you provision. Contact support to schedule a migration window.
BYOK to Managed: Data can be imported into NearSync's shared instance. Contact support for the migration process.
Data processing classification
Managed: NearSync acts as a data processor under GDPR. A Data Processing Agreement (DPA) governs this relationship.
BYOK: NearSync acts as a software licensor. NearSync provides application code - you host your own data. No DPA is required for the BYOK relationship (though you may need your own DPA with Supabase).