Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Event
GitHub Logo

Building Sustainable Open Source: The Harper Story

Discover how Harper successfully transitioned to a sustainable commercial open source platform. Ethan Arrowood details their split core licensing strategy, engineering velocity, and practical framework for building true community trust.
Event

Building Sustainable Open Source: The Harper Story

Ethan Arrowood
Head of Open Source
at Harper
June 9, 2026
Ethan Arrowood
Head of Open Source
at Harper
June 9, 2026
Ethan Arrowood
Head of Open Source
at Harper
June 9, 2026
June 9, 2026
Discover how Harper successfully transitioned to a sustainable commercial open source platform. Ethan Arrowood details their split core licensing strategy, engineering velocity, and practical framework for building true community trust.
Ethan Arrowood
Head of Open Source

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.

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.

Discover how Harper successfully transitioned to a sustainable commercial open source platform. Ethan Arrowood details their split core licensing strategy, engineering velocity, and practical framework for building true community trust.

Download

White arrow pointing right
Discover how Harper successfully transitioned to a sustainable commercial open source platform. Ethan Arrowood details their split core licensing strategy, engineering velocity, and practical framework for building true community trust.

Download

White arrow pointing right
Discover how Harper successfully transitioned to a sustainable commercial open source platform. Ethan Arrowood details their split core licensing strategy, engineering velocity, and practical framework for building true community trust.

Download

White arrow pointing right

Explore Recent Resources

Media Coverage
GitHub Logo

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Media Coverage
InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio, Staff Editor at InfoQ
Renato Losio
InfoQ Staff Editor
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Aug 2026
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Media Coverage

Harper Argues Against the Multi-System Stack and Releases 5.2

InfoQ examines benchmark results comparing co-located and serverless architectures, highlighting faster personalized-data paths, serverless advantages under heavy fan-out, and the performance implications of eliminating network hops between services at scale.
Renato Losio
Blog
GitHub Logo

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Cache
Blog
Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Person with very short blonde hair wearing a light gray button‑up shirt, standing with arms crossed and smiling outdoors with foliage behind.
Kris Zyp
SVP of Engineering
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp
Aug 2026
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp
Blog

Faster by Doing Less: How Harper 5.2 Engineers Database Performance

Harper 5.2 attacks database performance on three fronts: a per-worker record cache validated through lock-free atomic version slots, isolated commit scheduling to keep database writes off the application thread, and query planner improvements that route through the shortest available data path.
Kris Zyp
News
GitHub Logo

Harper Recognized as an Honorable Mention in the 2026 Gartner® Magic Quadrant™ for Cloud-Native Application Platforms

Harper’s inclusion highlights a broader shift toward integrated cloud-native platforms that unify data, caching, messaging, and application logic. The article explains how Harper’s distributed runtime and managed infrastructure reduce operational complexity, improve performance, and support modern applications and AI agents that require fast, reliable access to state, events, and tools.
Announcement
News
Harper’s inclusion highlights a broader shift toward integrated cloud-native platforms that unify data, caching, messaging, and application logic. The article explains how Harper’s distributed runtime and managed infrastructure reduce operational complexity, improve performance, and support modern applications and AI agents that require fast, reliable access to state, events, and tools.
Person with short dark hair and moustache, wearing a colorful plaid shirt, smiling outdoors in a forested mountain landscape.
Aleks Haugom
Senior Manager of GTM
News

Harper Recognized as an Honorable Mention in the 2026 Gartner® Magic Quadrant™ for Cloud-Native Application Platforms

Harper’s inclusion highlights a broader shift toward integrated cloud-native platforms that unify data, caching, messaging, and application logic. The article explains how Harper’s distributed runtime and managed infrastructure reduce operational complexity, improve performance, and support modern applications and AI agents that require fast, reliable access to state, events, and tools.
Aleks Haugom
Aug 2026
News

Harper Recognized as an Honorable Mention in the 2026 Gartner® Magic Quadrant™ for Cloud-Native Application Platforms

Harper’s inclusion highlights a broader shift toward integrated cloud-native platforms that unify data, caching, messaging, and application logic. The article explains how Harper’s distributed runtime and managed infrastructure reduce operational complexity, improve performance, and support modern applications and AI agents that require fast, reliable access to state, events, and tools.
Aleks Haugom
News

Harper Recognized as an Honorable Mention in the 2026 Gartner® Magic Quadrant™ for Cloud-Native Application Platforms

Harper’s inclusion highlights a broader shift toward integrated cloud-native platforms that unify data, caching, messaging, and application logic. The article explains how Harper’s distributed runtime and managed infrastructure reduce operational complexity, improve performance, and support modern applications and AI agents that require fast, reliable access to state, events, and tools.
Aleks Haugom