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

    Events

    What happened, and who asked for it.

    The feed

    • A live activity feed driven by the daemon's own event stream, with relative timestamps.
    • Filters by host and by outcome.
    • Called Activity until 0.1.7; the old path still redirects.

    The audit trail

    • Every audited action records the user who performed it.
    • The entry is written before the action runs and updated with its outcome, so an action that crashed the process still left evidence it was requested.
    • That ordering is deliberate: a log that only records successes is not an audit trail.

    Air-gapped

    • Written and read locally. Nothing is shipped anywhere for you to retrieve later.