Getting started
Use BayStore when the thing being sold is a named private instance, not seats in a shared tenant or raw hosting capacity.
Reference
Documentation for selling and operating product instances.
This entry point keeps public documentation separate from the operator console while exposing the concepts a buyer needs before launch.
Docs map
Start with the decision you need to make.
The public docs hub is written for buyers, founders, platform teams, and security reviewers evaluating whether BayStore's product-instance model fits their launch.
Products and setup
Orbit and OpenClaw share the same buyer-visible instance model: product, plan, order, access metadata, and lifecycle state.
Lifecycle and operations
Instances move through fixed states so buyers and operators do not have to infer what happened from a support thread.
Implementation boundary
What the current static launch covers.
| Topic | Public docs answer | Production dependency |
|---|---|---|
| Checkout | Checkout is documented as sandbox_placeholder; public pages do not claim live provider billing. | Provider-approved Stripe/PayPal setup, webhooks, tax, receipts, and merchant review. |
| Customer access | Sign in and sign up are public entry pages and intake paths. | Production identity provider, account issuance, sessions, and authorization policy. |
| Runtime operations | Operator actions are recorded by the API; public docs describe lifecycle intent and recovery metadata. | Worker-backed runtime mutation, queue processing, secrets, production clusters, and runbooks. |
| Status and API | Status explains surface readiness; API access is proxied from the web server and not presented as a public developer platform. | Deployment-specific status provider, API auth, rate limits, docs generation, and support process. |
Procurement docs are present, but still need approval.
The public site includes security posture, privacy, terms, DPA, and cookie drafts so buyers can see the expected review shape. They remain launch placeholders until the legal entity, jurisdiction, subprocessors, retention schedule, and approved commitments are filled in.
Use the checklist before saying production ready.
BayStore is ready as a static marketing and evaluation surface when the public content, routes, SEO, forms, and deployment headers pass. Production payment, auth, and runtime mutation need separate evidence.
Docs handoff: This static page is the public documentation entry for launch. A generated API reference, CMS, or full docs site can replace it later without changing the marketing navigation contract.