Dedicated tenancy SOP
30-minute ops time + 24-hour DNS = 1-2 day onboarding to a customer's own Supabase project in their chosen AWS region. For Enterprise customers electing data residency.
What we commit to
These commitments are written into the MSA / DPA at signing — published here so prospects can verify without needing the full playbook.
- Customer picks the AWS region (Frankfurt, Dublin, Stockholm, Mumbai, Virginia, etc.)
- Customer's data lives in their own Supabase project — never co-mingled
- End-to-end onboarding 1-2 days (30 min ops + 24h DNS propagation)
- Customer admin gets dedicated workspace URL + named contact on day 1
- Region locked in MSA Schedule X (Data Residency)
Full runbook available under NDA
Full SOP covers: 7-step provisioning runbook (Supabase project creation, migration application, admin seeding, Vercel routing, DNS configuration, smoke testing, hand-off), per-step verification, cost model, ongoing-ops cadence (migrations, access reviews, restoration tests), and the common-issues debugging guide.
We previously published this runbook in full publicly. After a security review we've moved the implementation detail under NDA — pre-prepared, clickwrap NDA, typical turnaround 3 business days. The high-level commitments above stay public so you don't need the NDA pack just to verify the basics.
Request the full runbookPublic security artifacts (no request needed)
- ← Trust Center — controls, compliance status, verifiable parameters
- status.getleanos.com — real-time uptime + incident history
- Vulnerability disclosure policy — coordinated disclosure + safe harbor for researchers
- Subprocessors — every vendor that touches customer data