Skip to content
Home/How it works
Tides

Every instance moves through a named lifecycle.

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

01

Buy

Select Orbit or OpenClaw, choose a plan, and create an order tied to a customer record.

02

Provision

The instance enters `provisioning` while BayStore records desired commercial state and access metadata.

03

Operate

Health, backup metadata, suspension, resume, and upgrade intent remain visible as lifecycle transitions.

04

Recover

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

05

Retire

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

State tokens

The lifecycle vocabulary