Productized open-source
Turn a self-hosted tool into a commercial product offer without exposing buyers to cluster plumbing.
The harbor for product instances
Your product, moored in its own private bay.
BayStore sells isolated product instances through sandbox checkout and test-runtime observation. You buy a product; the API records each boundary step.
berth A-04 / local-test
orbit-prod-01
Orbit / Standard / test runtime
Sandbox checkout accepted
Test runtime instance observed
Health check passed
In the harbor
Products you can evaluate today
Each product is sold as an isolated instance with its own berth. Add a product family without changing how anyone buys.
Solutions
Build the buying path around the instance.
BayStore works best when the thing for sale is a private product instance with a clear commercial record, plan depth, access boundary, and lifecycle state.
Managed instances
Give each customer one named instance record, plan, status, and access metadata boundary.
Recoverable operations
Keep retries, suspension, upgrade intent, and recovery work visible as lifecycle operations.
Model, not claims
Proof-safe examples for evaluating the operating model.
These are illustrative scenarios for buyer education. They are not customer stories, endorsements, uptime results, or production deployment claims.
Orbit coordination berth
A buyer selects Orbit Standard, stages a sandbox order, and sees a named instance move through visible lifecycle state before production dependencies are approved.
single-tenant
test runtime
bounded access
What the current surface can honestly prove
Checkout remains sandbox_placeholder; this public site does not charge cards or configure production provider billing. Operator actions are recorded by the API; production runtime mutation remains deferred.
Tides
Explicit state, end to end
Every instance moves through a defined lifecycle along the tide. Nothing happens silently.
High tide
Buy
Pick a product and plan. Sandbox checkout records the intent; live provider billing remains deferred.
Inbound
Moor
An isolated instance is recorded in the test runtime.
At berth
Operate
Health checks, backup metadata, upgrade intent, and rollback paths stay visible without claiming production mutation.
Ebb
Recover
Suspend, resume, or record restore intent against backup metadata without claiming production mutation.
Trust boundary
Clear claims beat vague readiness.
BayStore separates public marketing, customer access, operator records, legal drafts, and production launch dependencies.
Self-hosted public bundleStatic HTML, CSS, JS, metadata, sitemap, and local brand assets.
No public console navDashboard and console files are not exposed through marketing discovery paths.
Sandbox checkoutNo card charge or production provider billing is claimed by this site.
No certification claimSecurity pages describe boundaries, not approved third-party compliance status.
Berths
Pick your depth
Each plan is a capability map - compute, storage, backup metadata, access, support marker. Not raw infrastructure.
FAQ
Questions buyers ask before a product-instance launch.
The answers keep the current static launch boundary visible while pointing to deeper resources.
Is BayStore a generic hosting platform?
No. BayStore is for selling named product instances with product, plan, order, access, and lifecycle state joined together. See the comparison page for the distinction.
Can the public site charge cards?
No. Checkout remains sandbox_placeholder; this public site does not charge cards or configure production provider billing.
Does BayStore claim production runtime automation?
No. Operator actions are recorded by the API; production runtime mutation remains deferred until a separate runtime implementation and deployment task is completed.
Where should a buyer start?
Start with Solutions if you are evaluating fit, Lifecycle if you need the state model, or the Launch checklist if you are planning production readiness.
Next berth
Map your product to a buyer-visible instance lifecycle.
Bring the product family, desired plan depth, security questions, and launch timeline. BayStore will keep production payment and runtime dependencies explicit.