SHOWCASES NEWS DOCUMENTATION CONTACT
BACK TO NEWS
POSTED ON June 10, 2026
BY Pears News
Hello Pear Boilerplates

What if a terminal application could update itself without relying on servers, package registries, or centralized infrastructure? Introducing Hello Pear Bare, a new boilerplate for building standalone Bare executables with peer-to-peer over-the-air updates built in. Package your application and runtime into a single binary, distribute it anywhere, and let updates flow directly between peers. This article explores the architecture behind the next generation of peer-to-peer software distribution.

Over many iterations between Keet and Pear we’ve distilled our proven peer-to-peer deployment architecture with the pear-runtime module for peer-to-peer over-the-air updates into a quick start boilerplate for P2P Desktop Applications: Hello Pear Electron. 

Announcing Hello Pear Bare, a quick start boilerplate for P2P Terminal Applications – standalone Bare executables with peer-to-peer over-the-air updates.

With this boilerplate we can make CLIs, REPLs, TUIs, daemons, services, transport hooks and more with P2P OTA update capabilities.

Where the Hello Pear Electron boilerplate embeds pear-runtime into Electron, the Hello Pear Bare boilerplate embeds it into Bare, the zero-core embeddable JavaScript runtime.

Application and runtime compile into a single standalone binary executable per OS & architecture with no peer dependencies – no reliance on Node.js, no need for Bare or Pear CLI to be installed on the user system. Updates are deployed peer-to-peer with Pear CLI and the standalone executables are replaced on user machines by the pear-runtime module.The standalones can be distributed via usual channels (website, apt-get, brew..) and in the next Pear CLI update they can be installed peer-to-peer with pear install pear://<key> – use npx pear-install pear://<key>  to preview.

The upcoming next major release of Pear CLI (v3) uses this exact architecture – it’s a Bare runtime standalone executable with P2P OTA updates via the pear-runtime module deployed with Pear CLI itself.

Follow the hello-pear-bare Readme to get started.

We’re excited to see what emerges from the ecosystem community.

Keep an eye out for future Pear Boilerplates, Hello React Native Boilerplate for peer-to-peer over-the-air updates on mobile is in the works.

Join us in the Pear Development group on Keet to catch up, ask any questions, and show us what you’re working on.

Office hour runs Wednesdays at 16:00 CET/CEST for dedicated Pear team response, but ask a question any time and help generally arrives.

Related entries
Pear Evolution

Pear is evolving. What began as a peer to peer application runtime inside the Pear CLI is now becoming something far more flexible: an embeddable runtime library that can integrate into any JavaScript environment. This shift marks a major step forward for the Pear ecosystem, making peer to peer over the air updates, distributed deployment, and Bare workers available beyond the CLI itself. In this article, we explore the history behind Pear, why the runtime architecture is changing, and what developers need to know as Pear moves toward a more modular and production ready future.

READ MORE
Where does your data actually live? The architecture behind PearPass’s no-cloud promise

Most password managers encrypt your vault and upload it to the cloud. PearPass does something radically different: your data never leaves your devices. No central server. No cloud copy waiting to be stolen. This deep dive explores the peer to peer architecture behind PearPass, from Hypercore and Hyperswarm to Autobase and end to end encrypted device syncing — and why removing the server changes everything.

READ MORE
P2P from Scratch — Part 1: The Internet is Hostile

You want two computers to talk directly to each other. No server in the middle, no middleman, no monthly bill. Sounds simple — the Internet is a network, after all. But the moment you try it, you discover something uncomfortable: the Internet was never designed for this. Here’s why, and how Hyperswarm punches through anyway.

READ MORE