Realtime coordination
Give a team its own Orbit workspace without blending data or runtime state with another customer.
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.
Stateful by default
Orders, subscriptions, provisioning, access, and recovery use explicit BayStore states instead of silent side effects.
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.
Related paths
Buyer fit
Orbit fits team workspaces that need private ownership.
Use Orbit on BayStore when the buyer expects one workspace, one subscription record, and clear status during setup, support, and recovery.
Private customer workspaces
Teams that need a dedicated coordination space with a named instance and buyer-visible access boundary.
You sell shared seats
If the product is purely a multi-tenant seat subscription, BayStore's instance lifecycle may add unnecessary ceremony.
Identity and routing
Production auth, custom domains, access policy, and workspace data handling need separate approval before go-live.
Launch path
How an Orbit intake moves forward
| Step | Buyer-visible output | Boundary |
|---|---|---|
| 1. Fit review | Product family, plan, expected workspace owner, and security questions are captured. | Sales/intake only; no account is created. |
| 2. Sandbox order | A product-instance order can be evaluated against the static pricing and lifecycle model. | sandbox_placeholder; no card is charged. |
| 3. Access handoff | Sandbox access metadata appears only after the instance reaches active. | Production routing and auth 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 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.