Core Concepts

Service Ownership

Which services own which APIs, frontends, and trust boundaries.

On this page

Service Ownership

This page is the concise source of truth for what each service owns today.

Frontends versus backends

SurfaceRepo / ServiceRole
Marketing siteuseCascade.ioPublic site, product language, early-access messaging
Docs sitedocsProduct and operator documentation
Headwaters UIHeadwatersMinimal human-auth frontend
Conduit UIConduitTenant/customer/staff panel frontend
Weir UIWeirOperator/admin frontend

Backend ownership

ServiceOwnsDoes not own
HeadwatersHuman identity, orgs, sessions, MFA, OIDC/OAuth, JWKSBilling, tenant policy, workload runtime
FabricTenant lifecycle, entitlements, policy bundles, signed actions, node licensingHuman identity, invoices, browser sessions
LedgerCatalog, subscriptions, checkout, billing provider syncTenant policy authority, node runtime
ConduitTenant-facing panel APIs and runtime-facing orchestrationCanonical billing state, canonical human identity
CascadiaNode runtime execution and local workload stateGlobal control-plane policy
BreakwaterMachine PKI and internal trust materialHuman auth, tenant billing
WeirOperator aggregation and admin workflowsCanonical source of truth for auth, billing, or tenant policy

Transport ownership

TransportOwner / Typical use
Public HTTPBrowser-facing surfaces and public docs/site
Internal mTLS HTTPService-to-service authoritative request/response
NATSAsync backend event propagation

Current frontend readiness

FrontendBackend readiness
HeadwatersClose enough for implementation now
ConduitClose enough for implementation now
WeirWait for the remaining durable-session and real-integration work