Automation runtime
Run workflows in a private instance without requiring buyers to operate infrastructure directly.
BERTH B-01
OpenClaw, moored as a private automation engine.
BayStore stages OpenClaw as 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.
What this berth includes
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
Buyer fit
OpenClaw fits teams turning automation into a managed product.
Use OpenClaw on BayStore when buyers need one private automation engine, explicit lifecycle state, and a commercial record around runtime operations.
Customer-owned automation
Teams packaging workflow automation for customers who should not operate cluster or provider internals.
You need raw infra resale
BayStore is not a broad hosting marketplace; it is strongest when the product-instance lifecycle matters to the buyer.
Runtime execution
Worker-backed mutation, queue processing, secrets, routing, and runbooks need separate production evidence.
Launch path
How an OpenClaw intake moves forward
| Step | Buyer-visible output | Boundary |
|---|---|---|
| 1. Runtime fit | Workflow family, expected volume, plan depth, and support expectations are captured. | Sales/intake only; no production runtime is changed. |
| 2. Sandbox order | A product-instance order can be evaluated against the static pricing and lifecycle model. | sandbox_placeholder; no card is charged. |
| 3. Operations review | Suspension, resume, upgrade, and recovery paths are mapped before production claims are made. | Worker completion, secrets, and routing remain deployment work. |
Plan comparison
Plan capabilities
Standard
4 GiBmemory
2 vCPU, 40 GiB storage. 7-day backup metadata. Sandbox access URL.
Moor in StandardPro
8 GiBmemory
4 vCPU, 120 GiB storage. 30-day backup metadata. Priority support marker.
Review Pro berth
Harbor questions
Common questions about OpenClaw on BayStore
Does each customer get a private OpenClaw runtime?
Each order creates one single-tenant OpenClaw instance record. Workflow state, access credentials, and lifecycle records are not shared across customers; live runtime wiring remains a separate launch dependency.
Can I suspend and resume the automation engine?
Yes. Suspension moves the instance record to the
suspended state, and resume records an explicit lifecycle transition back to active. In the current boundary these are API-requested operator actions that feed bounded launch evidence.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 berth do to an active instance?
The instance record enters the
upgrading state while capacity-change intent is tracked. Returning to active requires the appropriate runtime execution path in the launch environment. Proration is a billing configuration concern resolved at go-live.