Private beta · building in the open
We're building Alleex Cloud
in public.
Alleex Cloud is in private beta. The codebase, the design decisions, and the roadmap are visible on GitHub. That is the community right now — honest progress, open to read, open to critique.
What open means
Transparent by default
We ship code to a public GitHub repository, write decision records explaining why things are built the way they are, and surface the compliance posture of the platform on the compliance page. There are no vanity metrics on this page — no fabricated member counts, no fake event lists.
The repository is the ground truth. If you want to understand how Alleex Cloud works, read the source.
Private beta
Where we are right now
Alleex Cloud is in private beta. We are not running a public community yet because the product is not ready for that. Channels will open when we have something stable enough to invite people into.
Discord
A server for beta builders to share feedback and help each other. Opening as we expand the beta — not before it is ready.
Office hours
Live video sessions with the core team. Scheduled once the beta cohort is large enough to be worth the format.
Changelog
Every meaningful change to Alleex Cloud, written honestly. Will be linked from /changelog once the cadence is established.
Right now
How to follow progress today
- 01Star or watch the repo — github.com/burgeralexander/alleex-cloud. GitHub notifications are the most reliable way to track changes until there is a proper changelog feed.
- 02Open issues and discussions — Bug reports, design questions, and feature requests on GitHub Issues are read by the team. We do not have a separate forum.
- 03Build something — Request access and try the beta. Direct product feedback from real use is more valuable than any forum post.
Follow the build. Shape the product.
The best way to influence Alleex Cloud is to use it and tell us what is wrong. Private beta access is limited — request early.