No Servers, No Cloud, No Masters: Make P2P Apps with Pear

React Summit

React Summit 2026

Mikkel Malmberg

All it takes is a module and a CLI tool to build and deploy production peer-to-peer applications.In this workshop:<ul><li>Convert an existing React application so that it no longer needs a server to deploy</li><li>Prepare the application and setup deployment flow for production release</li><li>Go to production with multisig - decentralized quorom-based cryptographic signoff gated releases</li></ul>This is for anyone who builds with React or JavaScript and anyone who deploys applications.

JS Nation

JSNation 2026

All it takes is a module and a CLI tool to build and deploy production peer-to-peer applications. In this workshop:<ul><li>Build a realtime peer-to-peer application</li><li>Connect with others on your own application, completely peer-to-peer.</li><li>Understand how to deploy, including production practices, principles and tooling</li></ul>This is for anyone who builds with JavaScript and anyone who deploys applications.

Pear: Releasing Production P2P Apps

Web Engineering Summit

Web Engineering Summit 2026

Most apps treat the server as truth. Peer-to-peer flips that: state starts local, users carry the data, and shared truth emerges without routing every interaction through a central backend. Outline: - The normal React/backend model - Server/database as the source of truth - The local-first flip - Local state becomes the primary user experience - From local-first to peer-to-peer - Users replicate state directly instead of only syncing through APIs - Using a chat app as the running example, with quick comparisons to docs, boards, and media sharing - How shared truth emerges - User actions as signed operations in append-only logs - Deterministic app rules decide which operations are valid - Peers agree on ordering and can independently verify the resulting state - What this means for React developers - UI becomes a view over local replicated state - Reality check and takeaways - P2P does not remove backend complexity; it turns it into protocol and state design - Tradeoffs include availability, permissions, conflict handling, and migrations - These are normal apps with a different source of truth — and they're possible now Will keep it high-level, practical, and example-driven. Including some lessons from building real peer-to-peer apps like Keet.