Home > Engineering > Third Party Software > Pear
Pear
Pear is Holepunch’s peer-to-peer runtime, development and deployment platform for desktop, mobile and terminal apps. It builds on Bare and the P2P building blocks. Apps are distributed over the peer-to-peer network: a build is staged into a Hyperdrive, and running apps take over-the-air (OTA) updates from it.
Upstream moves fast; the Release Overview is the current truth.
Current form: Pear v3
Pear v3 (July 2026) finished the move away from the original pear run model:
pear runis removed, withpear release,pear init,presets,shiftanddrop. The globalPearAPI went withpear run; the Pear API page is kept in the docs for reference only.- The runtime is a library. It lives in the embeddable
pear-runtime, which the docs now call Pear OTA. An app embeds it instead of being launched by the CLI. - The CLI does deployment and installation. From v3 it is a standalone binary that keeps itself up to date over the air.
- The v2 module split is gone.
pear-electron,pear-bridge,pear-run,pear-messageandpear-updatesare archived. The desktop template,hello-pear-electron, usespear-runtimedirectly.
Apps still on pear run need migrating: the migration guide covers the move to Pear OTA.
Embedding and boilerplates
Upstream gives one boilerplate per kind of app:
- Desktop:
hello-pear-electron— Electron as a thin shell around a Bare worker runningpear-runtime. - Mobile:
pear-mobilewithpear-runtime-react-nativeandhello-pear-react-native(announced 15 September 2026). OTA covers the JavaScript bundle; native code still goes through the app stores. - Terminal:
hello-pear-bareembedspear-runtimein the Bare worker of a Bare CLI, with P2P OTA updates and standalone distributables built withbare-build;hello-pear-daemonruns the updater as a detached daemon for short-lived CLIs. - Shared local backend:
hello-pear-worker.
See pear-runtime for the library’s API.
CLI
The pear CLI is at v3.6.0 (15 October 2026; v3.7.0-rc.0 tagged), with about 19 commands: touch, build, stage, provision, multisig, seed, install, blind-peer, blind-relay, changelog, info, dump, cores, data, sidecar, identity, gc, versions and help.
The deployment flow:
pear touch— allocate a Pear link (stored asupgradeinpackage.json).pear build— a deployment folder with per-architecture artifacts.pear stage— for previews only, not production.pear provision+pear multisig— the production release, quorum-signed.pear seed— keep it available.
pear install <link> installs an app. From 3.4.0 the CLI also runs Holepunch’s own blind peer and blind relay (pear blind-peer, pear blind-relay). See the CLI reference rather than a mirror here.
See Also
- Docs: docs.pears.com (Pear, P2P and Bare tabs) — Release Overview · CLI reference · migration guide
- Repo: github.com/holepunchto/pear
- Embeddable library: github.com/holepunchto/pear-runtime · npm
pear-runtime - Mobile: github.com/holepunchto/pear-mobile · announcement
- Boilerplates: Hello Pear Boilerplates
- Announcement of the transition: Pear Evolution