Last verified: 28 September 2026

Sub-processors

Managed-cloud hosting-substrate adapters referenced by Sovern Cloud, auto-projected from the closed registry.

Generated from lib/registry/hosting-substrate-adapters-registry.ts · 9 managed-cloud adapters

`supabase-managed-cloud`

Managed Supabase Postgres (hosted project)

layer: database · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.supabase-managed-cloud · requiredExtensions: vector, pg_net · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`postgres-managed-cloud`

Managed PostgreSQL service (RDS / Neon / hyperscaler Postgres)

layer: database · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.postgres-managed-cloud · requiredExtensions: vector, pg_net · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`supabase-auth-managed`

Managed Supabase Auth / GoTrue (hosted project)

layer: auth · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.supabase-auth-managed · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`supabase-storage-managed`

Managed Supabase Storage API (hosted project)

layer: object-storage · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.supabase-storage-managed · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`redis-managed`

Managed Redis-protocol service

layer: cache-queue · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.redis-managed · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`resend-managed`

Resend transactional email SaaS API

layer: email-transport · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.resend-managed · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`cloudflare-managed`

Cloudflare edge ingress (managed)

layer: reverse-proxy-ingress · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.cloudflare-managed · compatibleTlsAdapters: acme-letsencrypt-dns01-cloudflare, managed-cert-external · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`alb-managed`

AWS Application Load Balancer (managed termination)

layer: reverse-proxy-ingress · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.alb-managed · compatibleTlsAdapters: managed-cert-external, byo-cert · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

`sentry-managed`

Sentry SaaS error ingestion

layer: observability-transport · provenance: managed-cloud · applicableModes: saas, on-demand, jv-bespoke · healthProbeKey: hosting.probe.sentry-managed · archive docs/audits/archive/decisions/tier-5-infra-ops.md OO.sub2#L3133-L3141

§ZAC closure

This page implements the §ZAC public sub-processor disclosure stub from docs/architecture/DECISIONS.md §ZAC (§OO horizon), driven by managed-cloud rows in the hosting-substrate adapter registry. Future GG.sub8 evidence-bundle generators will surface SOC 2 / ISO 27001 attestation status per managed-cloud adapter when attestation packs land.