Transitioning an established, closed-source company into a thriving open-source ecosystem is no small feat. In his recent talk at the Linux Foundation, Ethan Arrowood, Head of Open Source Engineering at Harper, detailed exactly how Harper made this leap with the launch of Harper v5. Driven by the core pillars of business viability and community trust, Harper’s journey provides a practical blueprint for sustainable commercial open source.
Here are the three major engineering and strategic takeaways from the Harper story:
1. The Split-Core Licensing Strategy
To successfully balance corporate sustainability with open-source values, Harper adopted a split-core distribution model:
- Harper Core: The fully featured, production-ready core platform is entirely open source under the permissive Apache 2.0 license.
- Harper Pro: Additional enterprise-scale features (such as replication and certificate management) are source-available under the Elastic License v2 (ELv2).
- Harper Fabric: A fully managed SaaS hosting platform that drives company revenue and funds development of the open core.
2. Prioritizing Engineering Velocity
Splitting a codebase while supporting legacy enterprise clients can severely disrupt a team. Harper overcame this by leaning into rock-solid engineering fundamentals: stabilizing builds and tests immediately, avoiding massive simultaneous refactors, and utilizing Git to cleanly cherry-pick fixes across distinct repositories.
3. Cultivating Proactive Community Trust
True open source requires active engagement, not just making source code viewable. Harper established transparent communication boundaries, utilizing Discord for chat and GitHub Discussions for technical RFCs. They also implemented a strict human-in-the-loop contribution policy, prioritizing human creativity over fully automated AI submissions while explicitly declaring which repositories accept external contributions.
Sustaining the Foundation
A key element of Harper's philosophy is actively giving back to the open-source projects they rely on daily, including the OpenJS Foundation, Node.js, and WinterTC. Neglecting the foundational layer of the open-source ecosystem introduces major operational risks to any business built upon it.






.webp)

