Open. Stable. Ready.
An upstream-first OpenBMC distribution — developed in Europe, shipped across the world — focused on Stability, Long-Term Maintenance, Testing, and Developer Enablement.
HPE Partnership
Canopy partners with HPE to bring OpenBMC to ProLiant Gen11 platforms — more details coming soon.
Why Canopy?
Upstream-First
Weekly rebases from OpenBMC ensure you get the latest features and improvements while staying closely aligned with the community.
Stability
Thoroughly tested six-month release cycles with comprehensive validation provide enterprise-grade stability for production deployments.
Long-Term Maintenance
Extended LTS support with security patches, critical bug fixes, and predictable support lifecycles for production environments.
Hardware-Tested
Every commit is tested on real hardware through automated CI, ensuring rock-solid reliability across supported boards.
Developer Enablement
Modern tooling, prebuilt binaries, streamlined configuration, and comprehensive documentation make development productive and enjoyable.
Transparent & Open
Fully open source with automated CI/CD pipelines, public test results, and complete transparency in development processes.
What Canopy Is Made Of
Three layers build one curated tree. The community provides the foundation, with platform-specific code on top.
Vendor patches
Customer and OEM-specific code, typically under NDA and not upstreamable. This layer stays in Canopy only.
In-flight patches
Open-source changes posted upstream and under review, not yet merged — SoC silicon-init and board enablement, for example. Pulled forward so features land sooner, and upstreamable over time.
Upstream OpenBMC
Merged, released community code — bmcweb, phosphor-*, webui-vue and the Yocto layers. The foundation.
One curated, buildable, hardware-tested tree. Because we develop upstream-first, in-flight work flows down into the base as it merges — only the private vendor layer stays with us for good.
Release Channels
The same tree, delivered at the balance of freshness and stability your deployment needs.
Bleeding Edge
main
Newest of everything, integrated continuously.
- Tracks upstream main with weekly rebases, plus in-flight and vendor patches
- Freshest features, least hardening
Rolling Release
every 6 months
A stabilised snapshot on a fixed cadence.
- Tagged source with release notes and a hardware test report
- Bug and security fixes between releases
LTS Release
every 2 years
A release promoted to long-term support.
- Security and critical fixes only, backported for 5 years
- No feature churn — API and behaviour held stable
Release Strategy
Rolling releases every 6 months with LTS support every 4th release
Supported As Long As You Need
A new LTS branch every two years, each maintained for 5 years — and we carry the migration between them, so a product never runs out of support.
Five years per branch
Every LTS branch carries security patches and critical fixes for 5 years, and a new branch appears every two years — so there is always a maintained branch ahead of the one you are on.
We carry the migration
When you do move, we rebase the platform onto the new LTS. Vendor patches are carried forward, and anything already upstreamed arrives with the new base for free — so the delta you carry shrinks every cycle.
Proven by regression
The hardware regression suite runs on the new branch before you switch, proving functional parity on your boards rather than asserting it.
Never a support cliff
Because LTS branches overlap, there is always a maintained branch to move onto. Production never runs on an unmaintained tree.
How to Contribute
We're actively seeking collaboration with companies and individuals who share our vision for a stable, enterprise-ready OpenBMC distribution.
Hardware Contribution
Contribute your hardware for validation and testing on the Canopy stack. Help us expand our board support matrix and ensure your platform runs smoothly on enterprise-grade OpenBMC.
- Get your hardware validated on the stack
- Access to comprehensive testing infrastructure
- Long-term support for your platform
Proof of Concept
Interested in exploring this novel approach to OpenBMC distribution? We're looking for companies ready to start a Proof of Concept and validate the benefits of our upstream-first, LTS-focused model.
- Evaluate stability and long-term maintenance
- Test our weekly rebase workflow
- Shape the future of the project
Active Collaboration
Join us in building a sustainable, enterprise-ready OpenBMC ecosystem. We welcome collaboration on testing, validation, process development, and community building.
- Collaborate on release processes
- Contribute to testing infrastructure
- Help define best practices
Ready to Get Involved?
Reach out to discuss how we can work together to build the future of OpenBMC.