Comparison
Weave & Pear.
Pear is Holepunch's P2P runtime — install Pear, run a Pear app, ship updates over Hypercore. Weave is a Rust application stack you embed in your own services or agents.
| Dimension | Pear | Weave |
|---|---|---|
| Shape | Runtime + JS app shell + delivery | Composable Rust libraries |
| Distribution | pear://… app keys, install Pear once | Cargo crates / your service |
| Audience | JS app developers, end-user installs | Rust services, agent fabrics, infrastructure |
| Backbone | Hypercore + Hyperdrive + Hyperswarm | Trace + Locus + weave-swarm + Nexus |
| App protocol | Per-app | WOVEN (shared) or per-app over Trace/Lens |
| Agent surfaces | Not stated | First-class |
Pick Pear
Pick Pear if you want to ship a P2P consumer app and have Pear handle install + update + sandbox.
docs.pears.com →Pick Weave
Pick Weave if you're building services, agent fabrics, or infrastructure where you control the runtime and want Rust libraries you embed.
All primitives →Where they meet, where they diverge.
- Pear is a runtime: install it, run apps. Weave is a library set: compose it into your own runtime/service/agent.
- These are complementary deployment shapes — both off-chain, both peer-to-peer, both signed.