Code repositories are open. On-premises preview 2609.0.0-preview.4 is available now; it is not GA. The participant program and Azure-hosted PaaS are coming soon. Bug reports, feedback, and pull requests are welcome.
How we're building it
- Architecture Decision Records (ADRs) — Every major decision has a written record explaining what was decided, why, and what alternatives were considered. No black boxes.
- Research before decisions — We evaluate competing approaches and publish the research before committing to a direction.
- Planning in the open — ADRs, research documents, and design artifacts are tracked on GitHub in the public repos.
How to contribute
- Fork → branch → PR — Standard GitHub flow. No special tooling required. Public repositories are at github.com/CloudGrange.
- DCO sign-off — All commits require a Developer Certificate of Origin (DCO) sign-off. No CLA required — just a
Signed-off-by:line in your commit message. - Bug reports — Open an issue on the relevant repo. Include your deployment model, OS version, and log output.
- Feature requests — Use GitHub Discussions to propose features. Explain your use case and environment.
- Module contributions — Community modules can be developed independently against the module contract and hosted in the CloudGrange GitHub organization.
- OEM and partner modules — Hardware vendors and integration partners can ship their own modules without forking the core platform.
- Follow the build — Architecture walkthroughs and build updates are posted at blog.cloudgrange.com.
- Check the Changelog — The Changelog tracks releases and architectural decisions.
License
Apache 2.0
Use it, extend it, ship it. No surprises. No proprietary lock-in. Commercial and MSP use is explicitly permitted. No contributor license agreement — just a DCO sign-off on your commits.