Launching a peer-to-peer app is easy. Keeping it available after its developer leaves is harder.
PearBrowser users browse decentralized app catalogues and open each current release from one stable key.
Package the Hyperdrive and manifest. Pin it for availability; add the release to a catalogue for discovery.
PearBrowser sends a publisher-signed seed request. The Publish and Pin flow completes only after an accepted relay confirms replication.
Close the laptop. While a verified replica remains reachable, the same key still opens.
Apps open over Hyperswarm. Declared-public content can add an optional HTTPS bridge. Blind or P2P-only content stays off the public gateway.
Blind mode starts with client-side encryption. Relays receive sealed ciphertext, never the data key, and blind policy rejects known plaintext or key-material fields.
Peers understand keys and policy, not bespoke backends. Availability and blind custody are the base; app services stay opt-in.
Need relay-assisted catch-up? Experimental OutboxLog is opt-in. Operators register app namespaces and caps on a shared relay.
Signed updates carry namespace and writer. HiveRelay verifies both, enforces caps, then updates the current row. Events mark change, not truth, so clients catch up.
In a blind namespace, the versioned sealed-body envelope is mandatory. Known plaintext and data-key fields are rejected; keys stay with the app. Writer metadata remains visible.
Operators see connections, live apps, stored and served bytes, and relay health. Signed custody evidence remains separate.
When enabled for an archive-tier release, AutoHeal counts fresh anchor proofs as verified capacity. If capacity drops, it can recruit diverse replacements.
From catalogue to custody, HiveRelay turns availability into a verifiable handoff. Serverless for publishers. Provably blind for sealed workloads.