Release center

Go-live readiness

This is the final operator-facing release gate. It answers one question clearly: can OmniLaunch leave validation without breaking payment, delivery, or deployment?

release-capable

4/4 providers configured

Delivery mode

LIVE

Current operating mode

Configured

Across all release blocks

Missing required

Must be zero before public release

Provider readiness

Every block below maps directly to a go-live dependency.

Postgres

mode: live · required for release: yes

configured

Stores projects, quotes, orders, delivery versions, deployment history, action requests, and audit logs.

GitHub

mode: live · required for release: yes

configured

Required in live mode to create repositories and publish generated site files.

Vercel

mode: live · required for release: yes

configured

Required in live mode to create projects and wait for production deployments.

Lemon Squeezy

mode: live · required for release: yes

configured

Hosted checkout enabled. Webhook signing secret is configured.

Operational checkpoints

Homepage, dashboard, admin, and status pages stay reachable.

Health endpoints stay green before deeper release restoration.

All release-critical providers are configured.

Payment and delivery stay restorable one block at a time.

Recommended operator order

1Keep production deployment stable while restoring product-grade UI.

2Restore runtime-safe business modules before deeper admin fanout.

3Only reintroduce heavier DB-backed stats after the shell is stable.

4Use this page as the final readiness view before public launch.