beakerbrowser/beaker

★ 6,753JavaScriptAudience · developerComplexity · 4/5LicenseSetup · hard

Mindmap

mindmap
  root((beaker))
    What it was
      P2P web browser
      Hostless apps
      No central server
    Core tech
      Electron
      Hypercore
      Hyperdrive
    Status
      Archived
      No active dev
      Historical reference
    Dev setup
      Node.js 12 plus
      Build tools
      burnthemall reset

mindmap root((beaker)) What it was P2P web browser Hostless apps No central server Core tech Electron Hypercore Hyperdrive Status Archived No active dev Historical reference Dev setup Node.js 12 plus Build tools burnthemall reset

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Study the architecture of a peer-to-peer browser as a reference for decentralized app research.

USE CASE 2

Explore how Hypercore and Hyperdrive were used to serve websites without any central server.

USE CASE 3

Build on the archived codebase to experiment with hostless web application concepts locally.

Tech stack

JavaScriptElectronNode.jsHypercoreHyperdrive

Getting it running

Difficulty · hard Time to first run · 1h+

Project is archived, building from source requires Node.js 12+ and system-level build tools on Linux or Windows.

MIT-licensed, use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Beaker was an experimental web browser built on top of Electron, the same technology used to build apps like VS Code. Its distinguishing idea was peer-to-peer hosting: instead of every website needing a server somewhere, Beaker let users publish and visit websites that lived on the devices of the people sharing them, using a protocol called Hypercore and Hyperdrive. The goal was to make it possible to build web applications that did not depend on any central host. The project is now archived and no longer in active development. The README opens with that notice, so anyone finding this repository should treat it as a historical reference rather than a working tool to adopt. When it was active, Beaker worked like a normal browser for ordinary websites while also supporting a set of extra APIs that let developers build what it called "hostless applications." Those apps could store and share data directly between users without routing through a server. The browser handled the peer-to-peer connections underneath so the developer did not need to manage that infrastructure manually. Installation was available through prebuilt binaries for the major platforms. Building from source required Node.js 12 or higher, plus some system-level build tools on Linux and Windows. The README includes the full build steps and notes a command called burnthemall that wipes and reinstalls all dependencies when the build gets into a broken state. The project was MIT-licensed and open to contributions. Its documentation lived on a separate website. The README mentions a few environment variables for development use, such as overriding where user data is stored and controlling debug logging. The project was backed through Open Collective.

Copy-paste prompts

Prompt 1

Help me understand how Beaker Browser used Hypercore and Hyperdrive to host websites without a server, explain the data-flow in plain terms.

Prompt 2

Based on Beaker Browser's architecture, help me design a peer-to-peer file-sharing feature for a desktop Electron app using Hypercore.

Prompt 3

Walk me through building a minimal Electron app that uses Hypercore to sync data between two machines without a central server, inspired by Beaker.

Open on GitHub → Explain another repo

← beakerbrowser on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.