Release status · Updated 13 November 2026
Website online.
Product release pending.
The marketing website is publicly available. The product has local implementation and deployment evidence. Public enrollment, payment and permission to manage customer production are separate milestones.
What has been exercised locally
- Signed release and customer approval workflows, with installation-specific authority.
- Docker deployments through scoped brokers and separate customer VM engines.
- Uptime Kuma and Gitea application test workflows, including persistent-data checks.
- A connected signup-to-installation rehearsal, an actual application update and management retirement that preserved the application.
- Backup, recovery, account and isolation checks in the local test environment.
The builder operated both roles in the connected rehearsal. It used local mail capture, cached images and a test connection between the Mac and Linux VM. ARM64 local execution and x86-64 emulation do not establish independent production qualification.
What must pass before release
Independent installation
A clean Linux x86-64 host, trusted artifact delivery, real image acquisition and written onboarding completed by someone outside the build process.
OpenIndependent security review
A qualified reviewer assesses the frozen release and privileged boundaries; findings are resolved and retested.
OpenPublic commercial journey
Production hosting, Linux-hosted signup provisioning, real email and payment delivery, approved policies and working account recovery.
OpenOperational acceptance
Production-like capacity, restore drills, monitoring, incident ownership and the required seven-day release-candidate soak.
Open