Subdomain Plan
Surviva follows the Kennis Capital subdomain architecture. Each subdomain serves a distinct audience surface.
Active Subdomains
| Subdomain | Status | Purpose |
|---|---|---|
suriva.health | Live | Marketing site |
app.suriva.health | Live | Application (health assessments, wellness tracking) |
docs.suriva.health | Live | Documentation wiki (this site) |
api.suriva.health | Live | FastAPI backend on Fly.io |
Planned Subdomains
| Subdomain | Phase | Purpose |
|---|---|---|
admin.suriva.health | Phase 2 | Practitioner verification, safety flags, audit log |
cms.suriva.health | Phase 2 | Manuscr CMS instance for health content |
console.suriva.health | Phase 3 | Developer portal, API keys, webhook config |
staging.suriva.health | Active | Staging environment for QA |
api-staging.suriva.health | Active | Staging API on Fly.io |
DNS Configuration
All subdomains use Cloudflare DNS with the following pattern:
| Record | Target | Proxied |
|---|---|---|
suriva.health | cname.vercel-dns.com | Yes |
app.suriva.health | cname.vercel-dns.com | Yes |
docs.suriva.health | cname.vercel-dns.com | Yes |
api.suriva.health | Fly.io anycast IPs | No (Fly manages TLS) |
Health Data Compliance
All Surviva subdomains serve content from EU West 1 (Ireland) infrastructure. User health data never leaves the EU region. This applies to:
- Supabase database (eu-west-1)
- Fly.io backend (eu-west region)
- Vercel frontend (edge, with data fetching from EU backend)