Skip to main content
Private P2PCapability-FirstContainer + WASI

Fungi

Build a private P2P device network for capability-first services.

Build your own encrypted device mesh, run services under explicit runtime policy, and control remote nodes from a local CLI or GUI.

Quick StartDownload Fungi CLIDownload Fungi App (GUI)

Basic Flow

Daemonfungi daemon

Start the local daemon.

Trustfungi security allowed-peers add <alias>

Allow only your own device.

Openfungi access open --peer <peer-id> filebrowser-lite-wasi

Open a remote app locally.

Why Fungi

Focused on private infrastructure, not generic sync features

Private Device Mesh

Connect your own machines through an encrypted peer-to-peer network without depending on a hosted control plane.

Capability-First Services

Run container and WASI workloads under explicit runtime, path, and port policy instead of broad daemon privileges.

Remote Control From Local CLI

Target a remote peer, manage its services, inspect its catalog, and open its published web app locally with a small command set.

Three Command Groups

Remote workflow: Service, Catalog, Access

Servicefungi peer admin service start --peer <peer-id> filebrowser-lite-wasi

Start the remote service.

Catalogfungi catalog list --peer <peer-id>

See what that peer publishes.

Accessfungi access open --peer <peer-id> filebrowser-lite-wasi

Open the web app locally.

Start Here

Beginner-first docs, then deeper references

3 Minutes: Build Your Private P2P Network

Connect two of your own devices, trust them safely, and verify the link with ping.

3 Minutes: Run A Remote Sandbox App

Start a sandboxed app on one device and open it locally from another device.

Reference Docs

Dive into manifests, remote control, diagnostics, gRPC, relay setup, and runtime details.