Tenants on PULSE
A tenant is an application team operating inside a defined PULSE boundary: approved source repositories, dedicated namespaces, platform-delivered credentials, constrained network and Kubernetes authority, and a reviewed public edge.
The application team owns its product workloads and release intent. The PULSE platform team owns the trust boundary around them—identity, Secrets delivery, storage, Kubernetes authority, network policy, and public routing. The durable ownership rules are in ADR-0004, ADR-0005, and ADR-0006.
Tenant catalog
| Tenant | Live environment | Public service | Production | Documentation |
|---|---|---|---|---|
| ScreamingFace | Dev on aks-dev, staging on aks-staging, production on aks-prod |
Online behind Cloudflare Access | Live, dark since 2026-09-30: fusion.screamingface.ai, leaderboard.screamingface.ai, aigw-admin.screamingface.ai behind Cloudflare Access (operators only); every tenant workload runs on production since 2026-10-03 (report-intake's production hostname pending the owner's tunnel row and Access application) |
Quick rundown · Evidence and status |
"Listed" means that a tenant has a supported platform deployment. It does not mean the service is production-ready, that every provider path is accepted, or that every future environment exists. Each tenant page states those boundaries explicitly.
The ownership split
| Application team | PULSE platform team |
|---|---|
| Application source, charts, images, runtime behavior, and provider-facing product contracts | Repository and namespace fences, immutable deployment pins, identity and edge policy, Secret delivery, storage, RBAC, NetworkPolicy, and platform evidence |
Routine tenant releases advance through checked Kargo automation under ADR-0008. Changes that cross the platform boundary need a separate reviewed platform change.
Platform-wide availability is shown on the PULSE status board. Tenant pages explain which checks apply to each service and what those checks do—and do not—prove.