Click Below to Get the Code

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

From Local to Distributed Multi-Node Cluster in Minutes

See how to take a local Harper app to a distributed, multi-node cloud cluster with simple deployment steps, built-in scaling, and an MQTT real-world demo.
Harper Learn
Tutorial
Harper Learn

From Local to Distributed Multi-Node Cluster in Minutes

Ivan R. Judson, Ph.D.
Distinguished Solution Architect
at Harper
November 14, 2025
Ivan R. Judson, Ph.D.
Distinguished Solution Architect
at Harper
November 14, 2025
Ivan R. Judson, Ph.D.
Distinguished Solution Architect
at Harper
November 14, 2025
November 14, 2025
See how to take a local Harper app to a distributed, multi-node cloud cluster with simple deployment steps, built-in scaling, and an MQTT real-world demo.
Ivan R. Judson, Ph.D.
Distinguished Solution Architect

In this week’s Harper Learn session, Solutions Architect Ivan Judson walks through how to take a simple local setup and deploy it to a fully managed, multi-node Harper cluster in just a few steps. You’ll see how a project that starts on your laptop—configured with static files, users, and basic access rules—can be pushed to the cloud and immediately scaled across nodes with Harper’s streamlined deployment workflow. Ivan demonstrates how configuration, access groups, and app logic seamlessly transfer from local to distributed environments, highlighting the power and simplicity of Harper’s fused platform.To wrap up, Ivan gives a sneak peek of next week’s session by sending an MQTT message that triggers a real-world action—offering a glimpse into how Harper enables fast, event-driven applications. Whether you're building locally or deploying globally, this episode shows how quickly you can go from development to distributed production with Harper.

Resources
Follow Along with Harper Learn: https://github.com/HarperFast/harper-learn
Get Help on Discord: https://www.harper.fast/discord
CLI Remote Operations: https://docs.harperdb.io/docs/deployments/harper-cli#remote-operations

In this week’s Harper Learn session, Solutions Architect Ivan Judson walks through how to take a simple local setup and deploy it to a fully managed, multi-node Harper cluster in just a few steps. You’ll see how a project that starts on your laptop—configured with static files, users, and basic access rules—can be pushed to the cloud and immediately scaled across nodes with Harper’s streamlined deployment workflow. Ivan demonstrates how configuration, access groups, and app logic seamlessly transfer from local to distributed environments, highlighting the power and simplicity of Harper’s fused platform.To wrap up, Ivan gives a sneak peek of next week’s session by sending an MQTT message that triggers a real-world action—offering a glimpse into how Harper enables fast, event-driven applications. Whether you're building locally or deploying globally, this episode shows how quickly you can go from development to distributed production with Harper.

Resources
Follow Along with Harper Learn: https://github.com/HarperFast/harper-learn
Get Help on Discord: https://www.harper.fast/discord
CLI Remote Operations: https://docs.harperdb.io/docs/deployments/harper-cli#remote-operations

See how to take a local Harper app to a distributed, multi-node cloud cluster with simple deployment steps, built-in scaling, and an MQTT real-world demo.

Download

White arrow pointing right
See how to take a local Harper app to a distributed, multi-node cloud cluster with simple deployment steps, built-in scaling, and an MQTT real-world demo.

Download

White arrow pointing right
See how to take a local Harper app to a distributed, multi-node cloud cluster with simple deployment steps, built-in scaling, and an MQTT real-world demo.

Download

White arrow pointing right

Explore Recent Resources

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