Skip to main content

Deployment

High-level plane map for integrators and vendor operators. Detailed platform runbooks, Host layout, and hardening evidence stay in private ops packs — not on this public site.

Planes (conceptual)

PlaneRole for integrators
ManagementCatalog, licenses, portals, commerce admin APIs (Console / portals call here)
RuntimeActivate / validate / refresh / JWKS / config delivery for products and SDKs
Worker (async)Background jobs owned by the platform — clients do not call Worker HTTP
Local Relay (optional)On-site sync for constrained networks — Local Relay

Treat Management and Runtime as separate hostnames and contracts. Products should not hardcode Management URLs into Runtime SDK paths.

Integrator deployment checklist

Follow Production checklist: HTTPS Runtime base URL, environment-correct JWKS, secret redaction, offline/exp plan, typed degraded ≠ allow.

Explicitly out of public docs

  • Host → message-broker wiring and proprietary Host directory layout
  • Private TLS/secrets mount recipes and DR drills (platform operator pack)
  • Putting payment providers or Rabbit-style brokers on Runtime client critical paths

Next steps