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
  • Reference

    Dashboard & main menu

    The guide is organised by task. This page goes the other way: find the button you are looking at, and jump to the section that explains it.

    5 items on this page have no section in the guide yet. They are listed anyway rather than hidden, so the gap is visible.

    Main menu — top toolbar

    The protocol buttons across the top of the window, left to right, followed by the two dropdowns, the Hosts toggle and Settings.

    Dashboard — workspace sidebar

    The Workspace rail down the left of the Dashboard, plus the action bar and host tables in the main pane.

    Settings — category rail

    The left rail inside Settings, in the order the guide lists it.