Commercial state
Plans describe capacity, backup metadata, access eligibility, and support markers for one named instance.
Solution path
Managed product instances for buyers who need private state.
BayStore keeps each order tied to a named product instance, plan, lifecycle state, and access boundary so sales, support, buyers, and operators talk about the same object.
Why it matters
Dedicated instance buying needs more than a product card.
Customer visibility
The buyer can see lifecycle state and access metadata without seeing operator-only controls or internal runtime details.
Operational boundaries
Access metadata reflects the sandbox/test-runtime boundary unless a separate production deployment is completed.
Shared vocabulary
The instance record becomes the source of truth for launch state.
| Question | BayStore answer | Boundary |
|---|---|---|
| What did the buyer choose? | Product family, plan depth, and account metadata. | Checkout remains sandbox_placeholder; this public site does not charge cards or configure production provider billing. |
| Where is the instance? | Lifecycle state moves from pending to provisioning, active, suspended, failed, or deleted. | State is visible, but production runtime mutation remains deferred. |
| How does access work? | Access metadata appears when the instance reaches the appropriate lifecycle state. | Production auth/session setup is a separate deployment dependency. |
- Private workspaces, coordination tools, automation engines, and internal platforms sold as named instances.
- Teams that need buyer-friendly readiness language before production launch.
- Operators who want an audit trail before wiring production runtime actions.