Trust Home / System Status

System Status

Partial outage

Last updated: Aug 20, 2026, 12:00 AM UTC

Regions

RegionStatusP95 latency
US East (N. Virginia)major outage

Components

ComponentStatus

FHIR API

maintenance

Developer console

maintenance

Developer website and documentation

maintenance

Signup and onboarding

maintenance

Verification email delivery

maintenance

Deployment paths

Cernia supports seven first-class deployment paths plus a local-dev compose stack for developer environments. Roadmap items are tracked in the master plan (Phases 11d-11k).

Path / phaseTargetState
Local-dev compose Phase APath 3 hybrid (apps native, backend in Docker) Available
Local-demo smoke testpnpm smoke + pnpm test:e2e:smoke — proves the hybrid stack end-to-end Available
Local-dev compose Phase BTraefik + TLS terminationPending
Local-dev compose Phase CObservability wire-throughPending
Local-dev compose Phase DFully containerized apps profilePending
Phase-LD-D F1: admin-Dockerfileapps/admin standalone (port 3000) Available
Phase-LD-D F2: patient-Dockerfileapps/patient standalone (port 3001) Available
Phase-LD-D F3: trust-Dockerfileapps/trust standalone (port 3002) Available
Phase-LD-D F4: api-Dockerfile-verifyapps/api Dockerfile verified Available
Container-naming conventionname: cernia + cernia-* containers + com.cernia.* labels for Docker Desktop grouping Available
Path 1 SaaSCernia-hosted multi-tenantRoadmap
Path 2 KubernetesCustomer-managed (Helm)Roadmap
Path 3 Docker ComposeSingle-host productionRoadmap
Path 4 VM imagesOVA / VHD / AMI / qcow2Roadmap
Path 5 Linux nativeRPM / DEB packagesRoadmap
Path 6 Windows nativeMSI / Windows ServiceRoadmap
Path 7 Cernia LiteElectron desktopRoadmap

Containerized-apps Dockerfile readiness

Per-app status for the --profile containerized Docker Compose profile (Phase LD-D). Ready means the Dockerfile meets the hardening bar: multi-stage build, pinned base image, non-root user, scoped Dockerfile.dockerignore, healthcheck, and proper signal handling.

FileAgentStatusNotes
apps/api/DockerfileF4 ReadyHardened 2026-05-16 — tini PID 1, non-root uid 1001, pinned node:20-alpine, pnpm@9.0.0, scoped Dockerfile.dockerignore
apps/admin/DockerfileF1PendingSibling agent in flight
apps/patient/DockerfileF2PendingSibling agent in flight
apps/trust/DockerfileF3PendingSibling agent in flight
apps/cernia-ops/DockerfileF5PendingApp + package + API routes merged under Wave-E5 D2 (2026-05-16) by E1. Dockerfile (F5) is the remaining production-readiness piece.
infra/docker/docker-compose.yml — :containerized profileF6BlockedBlocked on F1+F2+F3+F4

Wave E4 agent fleet

Per-agent status for the Wave E4 fan-out (Phase 2 of the local-demo plan).

IDDeliverableStatus
B1E-5 RAG / reviewer auto-improvement loop — packages/voice-agent/src/improvement/*, admin /voice-agent/improvements/, REST /admin/voice-improvements/*, migration 039 Landed
B2E-8 Legacy schedule import (mirror-only, ADR-0049) — packages/scheduling/src/import/*, admin /scheduling/import/, REST /admin/scheduling/import/*, migration 040 Landed
B3E-N5 Wait-list (offer-when-slot-opens) — packages/scheduling/src/waitlist/*, patient /appointments/waitlist/, admin /scheduling/waitlist/, migration 041 Landed
B4E-N8 Post-visit satisfaction survey — packages/voice-agent/src/post-visit-survey/*, admin /quality/satisfaction/, REST /admin/surveys/*, migration 042 Landed
C1Wave E4 batch integration — merge B1–B4 into main, fix I-LD-STATUS-PENDING-LITERAL, tag v0.9-pre-wave-e5 Landed

Wave E5 agent fleet

Per-agent status for the Wave E5 fan-out (Phase 3 of the local-demo plan). Onboarding wizard + Cernia ops portal.

IDDeliverableStatus
D1E-11 Customer onboarding wizard — apps/installer/, packages/onboarding/, REST /onboarding/*, migration 043. 7-step: account / phone / use-case / Stripe Connect / BAA / SSO / migration. Pre-tenant capability-token model. Landed
D2E-12 Cernia ops portal (zero customer-data-bleed) — apps/cernia-ops/. 106 unit + 6 cross-browser tests. ADR 0054 + STRIDE. Landed
E1Wave E5 batch integration — D1 + D2 merged; ADRs F-U shifted +1; 6 new ADRs filed (0122–0127); 5 pre-existing failures fixed; coverage report shipped; tagged v0.9-local-demo. Done

Wave H agent fleet — white-label branding

Per-agent status for Wave H (the SaaS white-label correction). Sub-wave H1 Foundations runs first; H2 (apply to apps), H3 (cross-cutting), H4 (Cernia ops + integration) follow. Pulled from docs/implementation/WAVE-H-WHITE-LABEL-PLAN.md.

IDDeliverableStatus
H1-ATenant branding schema + DB migration + REST routes — TenantBrand in packages/core, 045_tenant_brands.sql, KyselyTenantBrandStore, tenant-brand-routes.ts. 47 + 22 + 24 tests including 4 cross-tenant adversarial regressions (ADR 0126). Landed
H1-B@cernia/branding package — BrandProvider / useBrand() / SSR resolveBrand() + branded header/footer/logo/attribution components. 96 net-new tests. STRIDE filed. Admin / patient / trust root layouts wrapped. H1-INT swap: TenantBrand re-exported from @cernia/core. Landed
H1-C@cernia/brand-assets — MinIO bucket cernia-brand-assets + 10-vector SVG XSS sanitiser + PNG/JPG re-processor + AV adapter + CDN URL builder. Wired into brand-asset-routes.ts. 113 net-new tests. Landed
H1-DBrand admin UI at /admin/settings/branding — 6 panels + live preview. Typed REST client. H1-INT swap: TenantBrand from @cernia/core. 76 unit + 14 Playwright tests. STRIDE filed. Landed
H2-*Apply branding to patient / admin / trust / login / email / SMS / PDF surfaces (7 agents). Unblocked: H1 Foundations landed via H1-INT.Pending
H3-*Voice-agent persona + custom-domain TLS + SMTP from-address (3 sequential agents).Pending
H4-OPS / H4-INTCernia ops explicit branding + integration + visual regression. Blocked on H3; produces v0.95-white-label.Pending

Incident history (last 90 days)

No incidents in the last 90 days

Get incident notifications

Subscribe to status updates via email or RSS.

Subscribe