Click Below to Get the Code

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

Harper at Node.js Interactive 2017

Fred discusses Harper's experience at Node.js Interactive 2017 in Vancouver, BC.
Blog

Harper at Node.js Interactive 2017

Fred Yoon
EVP of Corporate Strategy & Co-Founder
at Harper
October 9, 2017
Fred Yoon
EVP of Corporate Strategy & Co-Founder
at Harper
October 9, 2017
Fred Yoon
EVP of Corporate Strategy & Co-Founder
at Harper
October 9, 2017
October 9, 2017
Fred discusses Harper's experience at Node.js Interactive 2017 in Vancouver, BC.
Fred Yoon
EVP of Corporate Strategy & Co-Founder

Harper had its coming out party to the Node.js community last week as we were a sponsor at Node.js Interactive in Vancouver, British Columbia.  The event is one of many hosted by the Linux Foundation and the venue provided for an incredible backdrop to a very exciting event.

There were approximately 750 attendees this year and the enthusiasm around Node was palpable. Over the course of two days, more than 200 Node.js developers visited our booth to learn more about Harper and more than 50 downloaded our Community Edition.

It was very exciting to interact with the Node.js community and hear their feedback, and discuss the Harper roadmap.  We chatted with individual developers and learned about their journeys through Node.js and how Harper could be a step along that adventure.  People had some incredible ideas around what could be done with Harper, and it was amazingly fun to watch folks building on top of it right there on-site. There were also great suggestions on some really incredible solutions and libraries that we are excited to begin working to incorporate within Harper.

We enjoyed talking to the awesome folks at NPM like Laurie Voss (@seldo) and learning about different features and options at NPM for Harper.  It was also exciting to hear about different contributions companies like Microsoft, Google, Amazon, and Intel are making to the Node.js community. 

We feel very lucky to be part of such an open, enthusiastic, and cutting edge community.  Thank you to the Linux Foundation for hosting such a great event and one that the founders of Harper will never forget.  We look forward to returning next year. 

Harper had its coming out party to the Node.js community last week as we were a sponsor at Node.js Interactive in Vancouver, British Columbia.  The event is one of many hosted by the Linux Foundation and the venue provided for an incredible backdrop to a very exciting event.

There were approximately 750 attendees this year and the enthusiasm around Node was palpable. Over the course of two days, more than 200 Node.js developers visited our booth to learn more about Harper and more than 50 downloaded our Community Edition.

It was very exciting to interact with the Node.js community and hear their feedback, and discuss the Harper roadmap.  We chatted with individual developers and learned about their journeys through Node.js and how Harper could be a step along that adventure.  People had some incredible ideas around what could be done with Harper, and it was amazingly fun to watch folks building on top of it right there on-site. There were also great suggestions on some really incredible solutions and libraries that we are excited to begin working to incorporate within Harper.

We enjoyed talking to the awesome folks at NPM like Laurie Voss (@seldo) and learning about different features and options at NPM for Harper.  It was also exciting to hear about different contributions companies like Microsoft, Google, Amazon, and Intel are making to the Node.js community. 

We feel very lucky to be part of such an open, enthusiastic, and cutting edge community.  Thank you to the Linux Foundation for hosting such a great event and one that the founders of Harper will never forget.  We look forward to returning next year. 

Fred discusses Harper's experience at Node.js Interactive 2017 in Vancouver, BC.

Download

White arrow pointing right
Fred discusses Harper's experience at Node.js Interactive 2017 in Vancouver, BC.

Download

White arrow pointing right
Fred discusses Harper's experience at Node.js Interactive 2017 in Vancouver, BC.

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