Parahub is not a single server — it's a protocol. Anyone can run their own instance and connect to the network. Nodes share a public registry of organizations, profile migrations, and WoT verifications. No central authority.
Why federation?
If parahub.io goes offline, every other node continues working. Your data, your keys, your reputation — they don't depend on a single server. Communities can run their own instances while staying connected to the rest of the network.
Git as protocol
Every node keeps a signed Git repository with public records. Organization registrations, profile migrations, WoT verifications — all committed as JSON, signed with PGP, and anchored to Bitcoin via OpenTimestamps. No consensus, no gas, no tokens.
parahub-registry/ ├── node.json # Node manifest (PGP key, capabilities) ├── nodes/ # Known peers │ └── para.sh.json ├── organizations/ # Public organization records │ └── 01K7M4MD.json ├── verifications/ # Cross-node WoT verifications │ └── alice__bob.json ├── migrations/ # Profile migration records │ └── 2026-03-08_norn.json └── pgp-keyring/ # PGP public keys
Node
State layer. Signed JSON records, append-only, verifiable history.
Signal layer. Real-time inter-node notifications.
Communication layer. E2E encrypted messaging between nodes.
Profile migration
Moving to another instance? Your identity follows you. Four-party signature: old user, new user, old node, new node. Old address redirects to the new one. Verifications, contracts, items — exported and re-imported.
Federated search
Search for profiles and organizations across all connected nodes. Results come from local database and parallel queries to known peers.
Cross-node trust
Verify users on other nodes. Verification records are committed to Git and signed by both the verifier and the node. Trust propagates across the federation.