Skip to content
  • MangoFly

    A self-hosted WireGuard mesh. Devices connect straight to each other; the coordination server is one binary and a SQLite file, and never sees their traffic.

    encrypted WireGuard · peer to peerLaptopbehind home NATServerin a datacentrePhoneon mobile datacoordination serverone binary · one SQLite filecontrol plane only (TLS)keys · tunnel addresses · peer lists · sealed ICE candidatesholds no private keys · carries no traffic · cannot decryptdatacontrol
  • MangoDock

    Docker management with nothing on the hosts. Reaches each daemon over an ordinary SSH session — no agent to install, no port to open.

    The MangoDock dashboard showing three host cards with container state counts, CPU and memory gauges, a usage history and recent events
  • MangoWiFi

    A Wi-Fi 6/7/8 test bench. One binary runs as Console or Agent either side of the access point under test, measuring latency under real load.

    AP under testWi-Fi 6 / 6E / 7Agentstation side · real radioLAN receiveriperf3 -sConsoleUI · orchestrates · probes
  • Blog
  • Nothing phones home

    No telemetry, no analytics, no crash reporter, no account login. Check it with a packet capture on your own network.

    Download MangoSSH
  • Project
  • Download
  • Advanced

    Backups

    What you run, and where copies of it go.

    What can be backed up

    • A single volume, a whole stack, or a directory on the host.
    • Back up now, or on a schedule.

    Destinations

    • Add one or more destinations, each with its own repository and credentials.
    • Object storage is configured with an access key, so anything S3-compatible works.
    • Keeping a second copy somewhere else is a first-class option rather than an afterthought.

    Air-gapped

    • Point a destination at internal object storage — MinIO, or any S3-compatible service inside the enclave.
    • The backup helper image is carried in by the offline bundle, and its pull failure is tolerated so a backup still runs when the registry is unreachable.