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

    Registry

    Where images come from.

    Sources

    • Browse the official source, or any private registry you have stored a credential for.
    • Credentials live under Settings ▸ Credentials and are used for pulls as well as browsing.

    Air-gapped

    • This is the page the air gap is built around. Map docker.io — and ghcr.io, quay.io, and any other — to your own proxy cache under Settings ▸ Credentials ▸ Registry mirrors.
    • Every pull then goes through the mirror while keeping the original image name, so nothing downstream has to be rewritten.
    • Update checks ask the mirror, and stack deploys pre-pull through it.
    • The private-registry source browses the mirror, and any registry you hold a credential for.