Decision guide
Compare the base subscription with optional add-ons.
Launch-path copy is grounded in the same site setup stage setup used by the public site setup route.
Launch lifecycle
Public lifecycle map
From base subscription to DNS cutover without losing the thread.
Commissioner keeps discovery, site setup, DNS pause/resume, and add-on planning in one coherent public path. Logged-out visitors browse; signed-in subscription surfaces own the actual mutations.
Base subscription activates the service spine.
DNS pause/resume remains explicit.
Client account stays usable while site setup is pending.
Launch-path copy is grounded in the same site setup stage setup used by the public site setup route.
6
Stages
All
Browse-only public routes
Required
Signed-in mutation surface
Launch path timeline
The launch route exists to explain state transitions, not to hide them behind checkout.
Operational
Contract truth
Checkout starts the base service
The required base subscription turns on site setup, hosting, release train, and support queue handling.
- Commercial action Base subscription
- Route /pricing
- Why it matters Add-ons build on top of an already active service setup.
Operational
DNS pause is explicit
The flow waits at the DNS gate with clear instructions, then resumes after authoritative verification.
- Blocked reason Domain DNS not verified
- Resume event Authoritative DNS success
- Public evidence The site setup route surfaces the gate and next action instead of dead-ending.
Operational
Add-on planning survives the wait
The client can continue exploring add-ons and subscription states while site readiness catches up.
- Logged-out Browse-only
- Signed-in Subscription management
- Result Commercial planning continues without violating mutation boundaries.
Lifecycle disclosure
Setup truth
What stays visible throughout the launch path
The public path is allowed to expose state, blocked reasons, and next actions. It is not allowed to commit included access changes while logged out.
- Visible Current stage, blocked reasons, DNS instructions, and next actions.
- Hidden from public mutation Basket, subscription, and included access changes while logged out.
Launch sequence
The public lifecycle route rhythm
Each step has a deterministic state and a clear next action.
-
Setup truth
1. Compare + price
Understand base subscription versus add-on state deltas before checkout.
-
Operational
2. Complete base subscription
Site setup starts as soon as the required service setup is in place.
-
Operational
3. Site registration
Droplet and site registration move the tenant toward readiness.
-
Operational
4. DNS verification pause
The flow pauses at the domain gate with explicit instructions until verification succeeds.
-
Operational
5. Add-on state selection
Signed-in subscription surfaces can continue selecting add-ons and tier states during the wait.
-
Ready
6. Launch packet
Site URL, back-end URL, and credentials are issued only after readiness gates pass.
Setup truth
Pricing route
Carries the same commercial language into checkout.
- Route /pricing
- Purpose Checkout-ready
- Open route Start from pricing.
Operational
Site setup route
Displays the state machine, blocked reasons, and next actions for a live tenant flow.
- Route /site setup/{tenant_id}
- Purpose Lifecycle visibility
- Public setup The route must not dead-end or hide DNS blockers.
Needs attention
Status route
Publishes aggregate operational truth without exposing tenant secrets.
- Route /status
- Purpose Public-safe aggregate state
- Open route View aggregate service state.
Launch disclosure: the public route explains the lifecycle. Authenticated subscription surfaces are still the only place where purchasable changes can be committed.
Keep launch planning, pricing, and access on one path
Pricing activates the service spine; sign-in, compare, and packs remain the supporting public routes.