LogoLogo
  • Pear by Holepunch
  • Pear runtime
    • Command-Line-Interface (CLI)
    • Application-Programming-Interface (API)
    • Application Configuration
    • Troubleshooting Applications
  • Bare reference
    • Overview
    • Application-Programming-Interface (API)
    • Node.js Compatibility with Bare
    • Bare Modules
    • Troubleshooting with Bare
  • Guides
    • Getting Started
    • Starting a Pear Desktop Project
    • Making a Pear Desktop Application
    • Starting a Pear Terminal Project
    • Making a Pear Terminal Application
    • Sharing a Pear Application
    • Marking a Release
    • Making a Bare Mobile Application
    • Debugging a Pear Terminal Application
    • Creating a Pear Init Template
  • Building blocks
    • Hypercore
    • Hyperbee
    • Hyperdrive
    • Autobase
    • HyperDHT
    • Hyperswarm
  • How-tos
    • Connect two peers
    • Connect many peers
    • Replicate & persist
    • Manage multiple Hypercores
    • Share append-only databases
    • Create a p2p filesystem
  • Helpers
    • Corestore
    • Localdrive
    • Mirrordrive
    • Secretstream
    • Compact encoding
    • Protomux
  • Tools
    • Hypershell
    • Hypertele
    • Hyperbeam
    • Hyperssh
    • Drives
  • Apps
    • Keet
  • Examples
    • Bare on Mobile
    • React App using Pear
Powered by GitBook

Copyright © 2024 - 2025 Holepunch, S.A. de C.V. All rights reserved.

On this page
  • Table of Contents
  • Pear Runtime
  • Guides
  • How-tos
  • Building blocks
  • Helpers
  • Tools
  • Apps
  • Examples
  • Stability indexing

Pear by Holepunch

Last updated 17 hours ago

Pear loads applications remotely from peers and allows anyone to create and share applications with peers.

Pear by Holepunch is a combined Peer-to-Peer (P2P) Runtime, Development & Deployment tool.

Build, share & extend unstoppable, zero-infrastructure P2P applications for Desktop, Terminal & Mobile.

Welcome to the Internet of Peers

– Holepunch, the P2P Company

Table of Contents

Pear Runtime

References for Pear Runtime.

The Pear Runtime uses JavaScript runtime, which is a small and modular JavaScript runtime for desktop and mobile. To learn more, see .

Guides

Guides on using the Pear Runtime to build and share P2P applications.

How-tos

Simple How-tos on using the essential building blocks in Pear applications.

Building blocks

The essential building blocks for building powerful P2P applications using Pear.

Name
Description
Stability

A distributed, secure append-only log for creating fast and scalable applications without a backend, as it is entirely P2P.

stable

An append-only B-tree running on a Hypercore. Allows sorted iteration and more.

stable

A secure, real-time distributed file system that simplifies P2P file sharing and provides an efficient way to store and access data.

stable

A "virtual Hypercore" layer over many Hypercores owned by many different peers.

stable

The Distributed Hash Table (DHT) powering Hyperswarm.

stable

A high-level API for finding and connecting to peers who are interested in a "topic".

stable

Helpers

Helper modules can be used together with the building blocks to create cutting-edge P2P tools and applications.

Name
Description
Stability

A Hypercore factory designed to facilitate the management of sizable named Hypercore collections.

stable

A file system interoperable with Hyperdrive.

stable

stable

SecretStream is used to securely create connections between two peers in Hyperswarm.

stable

A series of binary encoding schemes for building fast and small parsers and serializers. We use this in Keet to store chat messages and in Hypercore's replication protocol.

stable

Multiplex multiple message oriented protocols over a stream.

stable

Tools

The following tools are used extensively employed in the day-to-day development and operation of applications built on Pear.

Name
Description
Stability

A CLI to create and connect to P2P E2E encrypted shells.

stable

stable

A one-to-one and end-to-end encrypted internet pipe.

stable

stable

stable

Apps

Applications built using Pear.

Examples

Collection of example applications that can be used as reference during development.

Stability indexing

Throughout the documentation, indications of stability are provided. Some modules are well-established and used widely, making them highly unlikely to ever change. Other modules may be new, experimental, or known to have risks associated with their use.

The following stability indices have been used:

Stability
Description

stable

Unlikely to change or be removed in the foreseeable future.

experimental

New, untested, or have known issues.

deprecated

Being removed or replaced in the future.

unstable

May change or be removed without warning.

Mirror a or a into another one.

A swiss-knife proxy powered by .

A CLI to run SSH over the .

CLI to download, seed, and mirror a or a .

: A peer-to-peer chat and video-conferencing application with end-to-end encryption.

: Reference applications for using Bare runtime on Android and iOS.

: Example application for building Pear applications using React framework.

Command-Line-Interface (CLI)
Application-Programming-Interface (API)
Application Configuration
Troubleshooting Applications
Bare
Bare Reference
Getting Started
Starting a Pear Desktop Project
Making a Pear Desktop Application
Starting a Pear Terminal Project
Making a Pear Terminal Application
Sharing a Pear Application
Releasing a Pear Application
Making a Bare Mobile Application
Creating a Pear Init Template
How to connect two peers by key with HyperDHT
How to connect to many peers by topic with Hyperswarm
How to replicate and persist with Hypercore
How to work with many Hypercores using Corestore
How to share append-only databases with Hyperbee
How to create a full peer-to-peer filesystem with Hyperdrive
Keet
Bare on Mobile
React App using Pear
Hypercore
Hyperbee
Hyperdrive
Autobase
Hyperdht
Hyperswarm
Corestore
Localdrive
Mirrordrive
Hyperdrive
Localdrive
Secretstream
Compact-encoding
Protomux
Hypershell
Hypertele
HyperDHT
Hyperbeam
Hyperssh
HyperDHT
Drives
Hyperdrive
Localdrive