Automation runtime
Run workflows in a private instance without requiring buyers to operate infrastructure directly.
Product berth
OpenClaw, operated as a private automation engine.
BayStore turns OpenClaw into a customer-owned instance with capacity plans, commercial lifecycle state, and explicit recovery handoffs.
Plan-led capacity
Buyers choose a capability map, not raw cluster settings or internal topology.
From $49 / mo
Standard capacity aligns to a managed product instance with sandbox access and lifecycle visibility.
Capabilities
What OpenClaw gets on BayStore
ProvisioningOrder intent becomes a visible instance record before runtime access is shown.
OperationsSuspension, resume, upgrade, and recovery remain explicit lifecycle transitions.
BoundaryBayStore exposes the commercial and operational contract without leaking provider internals.
Related paths
Capacity
Plan capabilities
Trial
2 GiBmemory
1 vCPU, 10 GiB storage. Community support. No backup metadata.
Standard
4 GiBmemory
2 vCPU, 40 GiB storage. 7-day backup metadata. Sandbox access URL.
Pro
8 GiBmemory
4 vCPU, 120 GiB storage. 30-day backup metadata. Priority support marker.
FAQ
Common questions about OpenClaw on BayStore
Does each customer get a private OpenClaw runtime?
Yes. BayStore provisions one single-tenant OpenClaw instance per order. Workflow state, access credentials, and lifecycle records are not shared across customers.
Can I suspend and resume the automation engine?
Yes. Suspension moves the instance to the
suspended state and stops active processing. Resume is an explicit lifecycle transition back to active. Both actions are recorded by the operator.Is the runtime access URL for production use?
The current access URL is a sandbox boundary. Production routing, custom domains, and provider-approved network configuration remain separate launch tasks.
What does upgrading the plan do to a running instance?
The instance enters the
upgrading state while the new capacity is applied. It returns to active once the transition completes. Proration is a billing configuration concern resolved at go-live.