2 x Intel Cascade Lake 24 Core In the beginning 2019 2019 100% Cloudflare servers on AMI BMC • Closed source, binary only • Beholden to server vendor for: ◦ Bug and vulnerability fixes ◦ Feature add / removal • Requests go "round trip": ◦ CF > Vendor > AMI > Vendor > CF ◦ Can take weeks or even months
2020 First OpenBMC development engineer hired • Engineers with OpenBMC experience are rare ◦ A smart embedded systems engineer can learn it ◦ TIP: search for resumes with the word “yoctoˮ • Pitfall: Proprietary Binary Libraries ◦ Used server vendor's binary library to speed development ◦ No access to source for that portion of the image ◦ "Don't control your own destiny" Same as AMI firmware) Generation 10 Servers AMD Rome 48-core
factory installed on all Gen 11 purchases •Limited resources meant limited coverage of legacy SKUs •Dev team expanded to three ◦ Ideal minimum team size to maintain tribal knowledge •Separate OpenBMC images for all SKUs ◦ 2 x edge servers & 4 x core server SKUs ◦ Specialty SKUs: ARM & GPU ◦ Added support for passively cooled GPUs Generation 11 Servers AMD Milan 64-core
open sourced as Project Argus • Allows reuse of code between images • Enables use of lower cost non PCIe Gen5 PCB Generation 12 Servers AMD GenoaX 96-core Cloudflareʼs OpenBMC Journey - PremDay 2026 * Datacenter Secure Control Module
integrated AI coding tools • Automated unit testing • Support for new SKUs accelerated ◦ ARM image took days vs. weeks • Accelerate porting older images to newest OpenBMC version • AI tools are a force multiplier - they donʼt replace people • Unified firmware image between Gen 12 and Gen 13 AIDriven Development Efficiency & Reliability Cloudflareʼs OpenBMC Journey - PremDay 2026