BayStore starts with Orbit and OpenClaw. Each product family gets the same commercial lifecycle, berth model, access boundary, and recovery language.
Each product is sold as an isolated instance with its own berth. Add a product family without changing how anyone buys.
A managed Orbit instance for teams that need a private workspace with clear lifecycle state. Single-tenant, recoverable, plan-mapped.
A private OpenClaw engine packaged as a BayStore product instance, without exposing infrastructure internals. Plan-led capacity map.
A mature product-instance offer needs more than a checkout button. It needs a product family, a plan, an owner, an access boundary, and an operating state that a buyer can understand without reading infrastructure logs.
| Question | Orbit | OpenClaw |
|---|---|---|
| Primary buyer need | Private coordination workspace for a team or customer account. | Private automation engine for workflow execution and operational handoffs. |
| Typical launch concern | Workspace isolation, access URL, backup metadata, and user onboarding boundary. | Runtime capacity, network routing, suspension/resume behavior, and operational recovery. |
| Best first plan | Standard for a proof-safe private workspace evaluation. | Standard when buyers need sandbox access and a concrete lifecycle record. |
| Escalate to sales when | Custom domain, security review, or multiple customer instances are part of the launch. | Workflow volume, runtime execution, or production routing needs approval before go-live. |
The marketing site does not create production accounts, charge payment methods, provision production clusters, or approve legal/security commitments. Those remain separate launch tasks with their own evidence.
Bring the product, berth target, expected buyer, launch timeline, and any security review requirements.