Launch Readiness
Confirm what must be ready before internal or customer launch.
Launch Readiness
Use this page before opening a workspace to internal teams, customer traffic, or a new feature rollout.
Readiness Categories
| Category | Ready means | Stop when |
|---|---|---|
| workspace | identity, owner, and team access are clear | no admin owner or stale access remains |
| features | at least one selected feature is effective | selected features are plan-blocked |
| keys | Publishable Key, CORS, and Secret Key ownership are clear | browser origins or key ownership are missing |
| billing | plan and subscription state are usable | subscription is past due, suspended, or unclear |
| content | enabled areas have minimum real content | enabled areas are empty or unowned |
| webhooks and analytics | owners know where failures and dropped events appear | failure ownership is unclear |
Launch Checklist
- owner and admins are current
- effective features match the launch scope
- required content or commerce records exist
- CORS, keys, analytics, and webhooks have owners
- billing state is not blocking
- support and moderation responsibilities are assigned
Stop Conditions
Pause launch when any required item is blocked, when plan-blocked features are still part of the launch promise, or when nobody owns customer-facing failures.
Treat readiness blockers as launch blockers. Fix the owner, feature, key, billing, content, or support gap before expanding exposure.
Next Actions
- If access is unclear, return to Workspace Setup.
- If features are blocked, return to Feature Planning.
- If keys or domains are blocked, return to Integrations & Keys.