Support and operations
Runbook-level guidance for the runtime first, then the console.
Support follows the same boundary as the product. Validate runtime health locally first, then troubleshoot console connectivity or private deployment routing if your plan includes it.
| Component | Endpoint | Purpose |
|---|---|---|
| Runtime | /healthz | Liveness check for the runtime process. |
| Runtime | /readyz | Readiness check that confirms policy is loaded. |
| Runtime | /v1/bundle/status | Current runtime bundle or policy status. |
| Console | /healthz | Console health check when the console is self-hosted. |
Quick diagnostics
curl http://localhost:8080/healthz
curl http://localhost:8080/readyz
curl http://localhost:8080/v1/bundle/statusCommon failure patterns
- Runtime is up but readiness fails because no policy has loaded yet.
- Growth runtime cannot fetch policy because the console URL or runtime token is wrong.
- A private Enterprise deployment exposes the console but the ingress or reverse proxy path is incomplete.
Starter
Docs-first onboarding for teams evaluating the open-source runtime.
Growth
Hosted console operations plus direct support for account and rollout questions.
Enterprise
Custom deployment planning and support for private runtime and console environments.