Every instance moves through a named lifecycle.

BayStore keeps commercial intent, provisioning state, and observed runtime aligned. The buyer sees where the instance is and what boundary is active.

The tide journey

Explicit state, end to end

Nothing happens silently. Each stage is a named position on the tide.

High tide

Select a product and berth. Order intent is confirmed — instance enters pending.

Inbound

The instance enters provisioning. Domain, TLS, and access metadata are tracked as launch dependencies.

At berth

Instance is active. Health checks, backup metadata, upgrade intent, and rollback paths stay visible without claiming production mutation.

Ebb

Suspend, resume, or record restore intent against backup metadata. State is preserved, not overwritten.

When a readiness gate fails, state is preserved. Operators retry, roll back, or restore instead of overwriting the record.

Deleted instances remain represented by terminal state for audit and commercial reconciliation.

State tokens

pendingprovisioningactiveupgradingsuspendedfaileddeleted

These tokens are the same across every BayStore surface — catalog, customer dashboard, and operator view. Nothing is translated or hidden.