Operational status

A public status surface for a product that cares about trust, not just demos.

OrbitForge treats status as more than server uptime. Public routes, health checks, domain readiness, and release parity all contribute to whether the product is actually safe to share.

Hosted app

Operational

The public OrbitForge site and workbench are served through the hosted deployment target.

Custom domain

Operational

orbitforge.dev and www.orbitforge.dev are configured as production-facing domains.

Health endpoint

Available

Machine-readable status is exposed through /api/health for deployment and uptime checks.

Provider lanes

Configurable

Local and hosted model providers can be enabled per deployment instead of being hard-wired into the public site.

What healthy means

A polished public launch needs operational discipline around content, routes, and recovery.

Keep the public site useful even when no local model endpoint is reachable.

Treat route health, docs, and pricing parity as part of product uptime.

Use the release gate before public changes that affect multiple surfaces.

Open health endpoint Review deployment guide