P2P DocsP2P
The peer-to-peer building blocks—Hypercore, Hyperswarm, Autobase, Hyperbee, Hyperdrive, HyperDHT, and Corestore—independent JavaScript modules for storage, discovery, and replication, usable with or without Pear.
P2P is the peer-to-peer building blocks: Hypercore for append-only logs, Hyperbee and Hyperdrive built on top of it, Hyperswarm and HyperDHT for finding peers, Autobase for multi-writer collaboration, and Corestore for managing many cores at once. Each one is an ordinary JavaScript module with no special status—install it with npm and use it like any other dependency.
They run on Bare, the zero-core JavaScript runtime, which is why the same storage and networking code works unchanged on desktop, mobile, or terminal. And they're what Pear, the peer-to-peer platform, is built on top of—if you want to ship what you build here as an app with over-the-air updates, that's what Pear adds.
Where to go next
Getting started
A type-along tutorial: build a peer-to-peer chat app from five files, then reshape it into a production scaffold.
Connect to peers
Dial a peer by key with HyperDHT, or join topics with Hyperswarm.
Store and replicate
Persist and replicate with Hypercore, manage many cores with Corestore, and share databases with Hyperbee.
Building blocks
Hypercore, Hyperbee, Hyperdrive, Autobase, HyperDHT, and Hyperswarm—the reference for every module.
How the stack fits together
From the native C foundations up through Bare, the building blocks, and Pear to the apps you run.
Ship it with Pear
Peer-to-peer app distribution, over-the-air updates, and a CLI to stage and release—running on the same core you build here.