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:

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:

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:

  1. pear touch — allocate a Pear link (stored as upgrade in package.json).
  2. pear build — a deployment folder with per-architecture artifacts.
  3. pear stage — for previews only, not production.
  4. pear provision + pear multisig — the production release, quorum-signed.
  5. 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