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.

Get StartedDownload Fungi CLIDownload Fungi App (GUI)

Basic Flow

Daemonfungi daemon

Start the local daemon.

Connectfungi ping <peer-id>

Verify the peer is reachable.

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

Access the remote service 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

Documentation paths by task

Quick Start

Initialize Fungi, trust peers, and start a local service with the shortest path.

Remote Service Control

Learn the `service`, `catalog`, and `access` flow for controlling remote nodes and opening remote web apps locally.

Services And Runtimes

Understand manifests, exposure rules, Docker-compatible runtimes, and WASI services.