Tag
P2p tools
5 reviewed tools: 5 free or open source.
Order: free and open source first, then hosted products with a real free tier, then paid-led; catalog order inside each group, with quiet or archived repos last. Not a score, and no tool pays for its place.
5 tools
- TrysteroMIT serverless WebRTC rooms via Nostr/MQTT/BitTorrent/IPFS
Free / OSS · OSS/MIT · 2.8k GitHub stars
VerdictMIT serverless WebRTC matchmaking. Free forever; pick it when discovery without your own signaling stack is the point.
CatchVs PeerJS, Colyseus, PartyKit, and Gatho: discovery+P2P data library — not a rooms product, not a state-sync game server, not Durable Object rooms, not a process-per-room toolkit, not a PeerServer you host. NAT/TURN still bites some networks even after signaling succeeds. You still own matchmaking UX, presence policy, and anything that needs a true authoritative server.
- MatchboxMIT/Apache-2.0 Rust/WASM P2P sockets for Bevy + GGRS
Free / OSS · Apache-2.0 · 1.2k GitHub stars
VerdictMIT/Apache-2.0 Rust P2P for Bevy/GGRS. Free forever; you still host signaling.
CatchVs PeerJS, Trystero, and Colyseus: Rust/WASM P2P socket + signaling crates — not a JS-first rooms kit, not serverless Nostr/MQTT discovery, not an authoritative game-room framework. You still run matchbox_server (or your own signaling) so peers can find each other; NAT/TURN still applies. Bevy version pins matter (bevy_matchbox tracks Bevy releases).
- crocMIT secure peer file send — relay + PAKE
Free / OSS · OSS/MIT · 40.6k GitHub stars
VerdictMIT peer file send. Free forever; rclone the remotes, croc the person in the other room.
CatchVs rclone (*rsync for 70+ cloud remotes*): croc is *peer send*, not cloud sync/mount and not a backup vault. Default path uses a public relay (you can self-host). Code phrase is the trust; treat it like a one-time password, not a permanent share link.
- irohRust library that connects devices by public key over QUIC
Free / OSS · Apache-2.0 · 12.8k GitHub stars
VerdictThe building block for local-first or P2P features in a Rust app — plan your own relay before you ship.
CatchRust first: other languages go through the separate iroh-ffi bindings, which trail the core (iroh-ffi v1.1.0, July 2026). The free public relays run by n0 are rate-limited, shared by everyone and come with no uptime guarantee — the project itself says they are for development and testing. For production you either run your own relay or pay for n0's hosted relays (Pro from $19/month, dedicated relays from $199/month per region). It is a connection library, not a VPN: if you just want your machines on one private network, Tailscale or NetBird is the simpler tool.
- PeerJSMIT browser P2P WebRTC with free cloud or self-host signaling
Free / OSS · Freemium · 13.5k GitHub stars · quiet 180d+
VerdictMIT P2P WebRTC. Free signaling path; not a rooms SFU.
CatchBrowser P2P WebRTC + optional free signaling — not LiveKit/mediasoup media-server rooms. Larger groups need a media server (SFU-class), not PeerJS alone. Distinct from LiveKit and mediasoup.
FAQ
- What is the top free pick among P2p tools?
- Trystero leads the Stack Gems list for P2p tools. Verdict: MIT serverless WebRTC matchmaking. Free forever; pick it when discovery without your own signaling stack is the point.
- How many P2p tools does Stack Gems review?
- 5: 5 free or open source. Each review has a verdict and an honest Catch; no tool pays for its spot.
- Which P2p tools can I self-host for free?
- Trystero, Matchbox, croc, iroh and PeerJS.
- Which P2p tools have the most GitHub stars?
- croc (40.6k), PeerJS (13.5k), iroh (12.8k), per GitHub on 2026-10-19. Stars measure attention, not fit; read the Catch.
- What is the catch with Trystero?
- Vs PeerJS, Colyseus, PartyKit, and Gatho: discovery+P2P data library — not a rooms product, not a state-sync game server, not Durable Object rooms, not a process-per-room toolkit, not a PeerServer you host.