Skip to content
Home/Harbor/OpenClaw
BERTH  B-01

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.

Start OpenClaw intakeRequest a demo
Use case

Automation runtime

Run workflows in a private instance without requiring buyers to operate infrastructure directly.

Commercial shape

Plan-led capacity

Buyers choose a capability map, not raw cluster settings or internal topology.

Plan anchor

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.
What this berth includes

Plan capabilities

Trial berth
2 GiBmemory

1 vCPU, 10 GiB storage. Community support. No backup metadata.

Start trial
Standard berth
4 GiBmemory

2 vCPU, 40 GiB storage. 7-day backup metadata. Sandbox access URL.

Choose berth
Pro berth
8 GiBmemory

4 vCPU, 120 GiB storage. 30-day backup metadata. Priority support marker.

Choose 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; production 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 operator-recorded actions, not proof of production runtime mutation.
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 a running 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.