Status and limits of the alpha
Alpha: for testing only; it does not yet meet the Cyber Resilience Act’s requirements. The EU’s Cyber Resilience Act allows unfinished software to be made available for a limited time for testing, with a visible sign that it does not comply. The alpha follows that: named testers, a fixed end date, this notice on every page. Do not run anything on it that you cannot afford to lose.
The limits of the alpha
Section titled “The limits of the alpha”- Podman hosts only. k3s clusters are built in the agent but refused by the hub’s alpha.
- No limit on the number of servers or twins in the open hub; the alpha builds Podman hosts only (above).
- Hetzner Cloud and ownpaas only. Other platforms come through providers.
- Named testers, each with an alpha key that ends on a fixed date (31 March 2027). After it, the hub keeps backups, restores, revoking access, deletion, export and security updates, and refuses new servers and twins.
- No public sign-up, and nothing is sold during the alpha.
Built and tested
Section titled “Built and tested”Built The hub, Podman hosts, twins, recovery tests, access on request, the agent principal and its audit, memory limits, the vai command, vaicoa-iaas with the KubeVirt provider, OpenShell sandboxes in the lab.
Built The rename: component names, environment variables (VAI_*) and the repository directory (.vaicoa/) carry the new name from the next release. The hub reads an environment’s old pbx/ directory for one release more, with a warning.
The stage-2 gate on Hetzner Cloud (20–21 October 2026) passed 79 of its 80 rows. “Built” here means it runs end to end in a lab on real servers; it is not a release.
- In progress Release signing keys. The keys’ ceremony (two offline keys) has not happened; the alpha runs on alpha keys.
- In progress The CLI over HTTPS. Today
vaireaches the hub through a WireGuard tunnel; HTTPS with mutual TLS was spiked, not built. See the admin plane. - Planned Approvals from the phone, in the Vaicoa app.
- Planned Hosted agent runs (Claude Code in the cloud).
- Planned k3s clusters in the hub.
- Planned The Hetzner passthrough and the first foreign provider.
- Planned Projects as objects in the hub, more than two per hub. See environments and projects.
- Planned Observability export. See observability export.
- Planned The public launch, with the source under Apache-2.0, planned for February 2027.
Your data
Section titled “Your data”The hub, its database and your cloud tokens stay in your project. Agents get no cloud token, no device key and no production access.