Documentation

Everything you need to run, harden, and extend PearDock, from first public key to multi-operator fleets and Holesail tunnels. Peer-to-peer by design: never open ports, expose Docker, or re-solve remote access for every host.

Concepts

How PearDock works

Deep explainer: P2P identity, hole punching, control vs data plane, security, and fleet model.

Start here

Quick start

One-line install.sh, systemd server, desktop client, and first peer connection.

Design

Architecture

HyperDHT control plane, protomux-rpc, handlers, and how Holesail sits beside RPC.

Production

Operator guide

systemd, roles, vault, feature flags, logging, compose stacks, backups.

Tunnels

Holesail

Reach services over hs:// with no inbound firewall ports.

Hardening

Security & threat model

Assets, trust boundaries, ACL, residual risks, operator checklist.

Reference

RPC & API

Method groups, pushes, roles, and protocol version negotiation.

Releases

Host matrix, bare-standalone, electron-forge, rolling tag, checksums.

Help

FAQ

Common questions about Pear, keys, Gatekeeper, AGPL, and v1→v2.

Install in one command

curl -fsSL https://install.peardock.boats | bash

Interactive installer: server (Linux + systemd + docker group) or desktop client. See Quick start and Download.

What is PearDock?

PearDock is decentralized Docker management on the modern Holepunch stack. There is no central control plane and no need to open or expose ports. The server listens on a HyperDHT keypair. Clients connect with its public key. Transport is Noise-encrypted. The desktop UI is a Pear/Electron app that feels like a full commercial Docker console, without SaaS tenancy or remote-access headaches.

Layer	Technology
Transport	HyperDHT (Noise-encrypted P2P)
RPC	protomux-rpc + compact-encoding JSON
Client	Pear desktop / Electron shell
Docker	dockerode
Port tunnels	Holesail (hs://)
License	AGPL-3.0 (same as Holesail)