Skip to content
Home/Harbor/Orbit
BERTH  A-01

Orbit, moored as a private coordination workspace.

BayStore packages Orbit as a named product instance with a clear commercial plan, isolated runtime boundary, and lifecycle state that stays visible from order to operation.

Start Orbit intakeRequest a demo
Use case

Realtime coordination

Give a team its own Orbit workspace without blending data or runtime state with another customer.

Lifecycle

Stateful by default

Orders, subscriptions, provisioning, access, and recovery use explicit BayStore states instead of silent side effects.

Plan anchor

From $39 / mo

Standard includes 2 vCPU, 4 GiB memory, 40 GiB storage, backup metadata, and sandbox access URL.

What this berth includes

What Orbit gets on BayStore

IsolationOne customer, one product instance, one lifecycle record.
AccessSandbox access metadata is exposed through the customer dashboard once the instance is active.
RecoveryBackup metadata and restore intent stay attached to the instance record.
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 Orbit on BayStore

Is my Orbit workspace isolated from other customers?
Yes. Each order creates one Orbit instance record with its own lifecycle state. Runtime state, access metadata, and backup records are not shared with any other customer instance.
How do I access my Orbit instance after it moors?
Once the instance reaches the active state, sandbox access metadata is visible in the customer dashboard. The current access URL reflects the sandbox boundary; production routing is a separate deployment task.
What happens if provisioning fails?
The instance enters the failed lifecycle state. Recovery is an explicit operation recorded by the operator. The instance record is preserved so the failure context is not lost.
Can I restore an earlier workspace snapshot?
Restore intent can be submitted against backup metadata retained by your plan tier (7 days on Standard, 30 days on Pro). The current public surface records the request and lifecycle state; production restore or rollback execution requires a separate approved runtime path.