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

Blog
GitHub Logo

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Blog
Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
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
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Jul 2026
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Blog
GitHub Logo

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Select*
Blog
AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
A smiling man with a beard and salt-and-pepper hair stands outdoors with arms crossed, wearing a white button-down shirt.
Stephen Goldberg
CEO & Co-Founder
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Jun 2026
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog
GitHub Logo

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Shell
Blog
A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Person with long wavy brown hair wearing a bright pink shirt with a teal trim, smiling outdoors in soft sunlight with blurred trees in the background.
Bailey Dunning
Forward Deployed Engineer
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Jun 2026
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog
GitHub Logo

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
A.I.
Blog
The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
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
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Jun 2026
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom