Capacity buyers can understand
BayStore translates product capacity into berth names, backup metadata, access markers, and support context instead of exposing raw cluster details.
Berths
Pick your depth.
Each berth 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.
BERTH 01
Trial
Free / 14 days
- Compute
- Storage
- Backup
- 1 vCPU, 2 GiB memory
- 10 GiB storage
- Community support
most moored
BERTH 02
Standard
$39 / mo
- Compute
- Storage
- Backup
- 2 vCPU, 4 GiB memory
- 40 GiB storage
- 7-day backup metadata
- Sandbox access URL
BERTH 03
Pro
$99 / mo
- Compute
- Storage
- Backup
- 4 vCPU, 8 GiB memory
- 120 GiB storage
- 30-day backup metadata
- Priority support marker
Berth matrix
Plan depth by capability
| 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.Procurement
Berth questions buyers need answered before approval.
These details keep the public berth page useful for finance, security, and platform reviewers while staying honest about the current sandbox launch boundary.
| Review topic | What the berth page commits today | What production go-live still requires |
|---|---|---|
| Billing status | Displayed prices are reference plan copy; no card is charged at this surface. | Provider billing, receipts, tax calculation, proration, and refunds configured before go-live. |
| Support scope | Community, Standard, and Priority describe intended support posture, not contractual terms. | Contractual response times, uptime targets, and escalation policy in an approved order or enterprise agreement. |
| Security and legal | DPA, privacy, terms, retention, subprocessor, and jurisdiction details are published in the legal center. | Signed agreement naming the contracting entity and governing jurisdiction for the deployment. |
Plan selection
Which plan should start the conversation?
Evaluating the model
Confirms product fit and lifecycle vocabulary without backup metadata or paid billing.
Trial intakeOne private instance
Adds backup metadata, sandbox access URL, and enough capacity for a proof-safe launch review.
Standard intakeMultiple stakeholders
Brings priority support marker, longer metadata retention, and procurement discussion into the same path.
Pro or sales-led intake
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 start intake?
The request captures product, plan, buyer context, and launch questions. In a sandbox evaluation, an instance can move through explicit lifecycle states such as
pending, provisioning, and active. Production account creation remains separate.Can I change plans later?
Yes. Plan upgrades move the instance record to the
upgrading state while capacity-change intent is tracked. Returning to active is represented by the bounded launch evidence 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 review an enterprise berth for capacity, security review, and production launch dependencies.