Binions has reached its first beta, and this page is an honest look at where it goes from here. The platform spent its alpha building the daemons, the event bus, and a broad set of integrations; the beta settled that feature set and hardened it. What remains is the road to the first stable, public release — 1.0. What follows is direction, not a dated set of promises.
Direction, not dates. This roadmap is indicative and may change as the platform matures. Nothing here is a commitment to a specific date or feature. The reliable signal for what has actually shipped is the Release notes.
Binions is in beta. The alpha line (the 0.x series) built the platform up—the thirteen daemons, the first end-to-end business automation, the edge and interactive layer, and the playbook control flow—and the first beta closed that phase by making the whole thing production-trustworthy: guaranteed-or-visible event delivery, a hardened security surface, and built-in observability. See v0.5.0-beta.1 for what that involved.
Three things were built in parallel alongside the daemons, and they are now live:
The first stable, public release is 1.0. It marks the point where the platform moves off the beta and onto a numbered, supported footing. Three things define that milestone:
| Milestone change | What it means for you |
|---|---|
| Numbered stable releases begin | Versioning follows a predictable, semantic scheme on a supported major line, so you can reason about upgrades and compatibility. See Version policy. |
| Raspberry Pi / 64-bit ARM packages arrive | The platform becomes available on 64-bit ARM hardware*, not just amd64, so a Raspberry Pi* can run the same packages as a server. |
| A long-lived, supported line | The beta’s hardening — delivery guarantees, the security surface, and observability — carries into a release intended to be run in production and supported over time. |
On licensing. Enforcement is already the default as of the beta — the underlying token-rotation and revocation system was built during the alpha, and the beta switched the default on. The licensing model itself stays simple all the way to 1.0: one set, one host. See Licensing & purchase.
As Binions grows, its core philosophy does not change. These are the design choices you can rely on across releases:
Looking further out — and in general terms only — the same patterns keep driving the platform forward. Expect more integration back-ends delivered through the multi-provider broker pattern, continued growth of the Modbus server mode and the other daemons as users ask for capabilities, and a steadily richer Claude skill as the tooling around the platform matures. The direction is steady, deliberate expansion along proven lines rather than sweeping change. As always, the specifics are subject to change, and the best way to follow real progress is to keep an eye on the release notes.
* Raspberry Pi and other 64-bit ARM hardware are supported from the public 1.0 release. The current alpha and beta packages are 64-bit x86 (amd64) only.