Early-stage software. Shurli is experimental and built with AI assistance. It will have bugs. Not recommended for production or safety-critical use. Read the disclaimer.
Documentation
FAQ

FAQ

Frequently asked questions about Shurli, organized by topic. Each section covers a different aspect of the project - from design philosophy to technical internals.

Note on comparisons: All technical comparisons in this document are based on publicly available documentation, specifications, and published benchmarks as of the date listed at the bottom. Software evolves - details may be outdated by the time you read this. If you spot an inaccuracy, corrections are welcome via GitHub issues or pull requests.

Sections

  • Design Philosophy - Why Shurli uses no accounts, no central servers, and no vendor dependencies. The reasoning behind self-sovereign identity and local-first design.
  • Comparisons - How different approaches to remote access compare: centralized VPNs, P2P mesh tools, relay architectures, and blockchain P2P stacks. Where Shurli’s design sits in the landscape.
  • Relay & NAT Traversal - How connections actually work: Circuit Relay v2, hole-punching, symmetric NAT, public vs self-hosted relays, and running your home node as a relay.
  • Security & Features - How pairing, verification, reachability grading, encrypted invites, and private DHT networks work.
  • Technical Deep Dives - Under-the-hood details: libp2p improvements Shurli has adopted, emerging technologies to watch, and the Go vs Rust trade-off.

Last Updated: 2026-02-24