Capacity buyers can understand
BayStore translates product capacity into plan names, backup metadata, access markers, and support context instead of exposing raw cluster details.
Berths
Pick your depth.
Each plan is a capability map - compute, storage, backup metadata, access eligibility, and support marker. Checkout remains a sandbox boundary until production provider billing is configured.
Prices are static launch copy
Checkout remains sandbox_placeholder; this public site does not charge cards or configure production provider billing.
Not a raw infra invoice
Use the comparison page and launch checklist to decide whether the product-instance model fits your selling motion.
Berths
Pick your depth
Each plan is a capability map - compute, storage, backup metadata, access eligibility, and support marker. Not raw infrastructure.
most moored
BERTH 02
Standard
$39 / mo
- 2 vCPU, 4 GiB memory
- 40 GiB storage
- 7-day backup metadata
- Sandbox access URL
BERTH 03
Pro
$99 / mo
- 4 vCPU, 8 GiB memory
- 120 GiB storage
- 30-day backup metadata
- Priority support marker
Comparison
Plan matrix
| Capability | Trial | Standard | Pro |
|---|---|---|---|
| Products | Orbit or OpenClaw | Orbit or OpenClaw | Orbit or OpenClaw |
| Backup metadata | None | 7 days | 30 days |
| Custom domain eligibility | No | Optional | Included marker |
| Support | Community | Standard | Priority marker |
Sandbox boundaryCheckout remains
sandbox_placeholder; this public site does not charge cards or configure production provider billing. Displayed prices and plan names are static marketing copy for the current surface.
Harbor questions
Common questions
Is each instance single-tenant?
Yes. Each purchase creates one named product instance scoped to one customer. No runtime state, access credentials, or lifecycle records are shared between customers.
Is checkout live yet?
No. The current surface uses a
sandbox_placeholder checkout boundary. Production payment processing through Stripe or PayPal requires a separate provider configuration step that has not yet been completed. Purchasing via this site does not charge a card.What happens after I moor?
The instance moves through explicit lifecycle states:
pending → provisioning → active. Once active, sandbox access metadata is visible in the customer dashboard. If provisioning fails the instance enters failed and recovery is an explicit operation.Can I change berths later?
Yes. Plan upgrades move the instance record to the
upgrading state while capacity-change intent is tracked. Returning to active requires the appropriate runtime execution path in the launch environment. Proration logic is a billing configuration concern that applies at go-live.How are backups handled?
Backup metadata is retained according to the plan tier: 7 days on Standard, 30 days on Pro. Restore intent is attached to the instance record; production restore execution requires a separate approved runtime path.
Do prices include tax?
Displayed prices are pre-tax reference figures. Applicable taxes depend on jurisdiction and will be determined at the time of live billing configuration. No tax calculation occurs in the current sandbox boundary.
Map a plan to your first product instance.
Start with a trial berth or contact sales to discuss capacity, security review, and production launch dependencies.