Skip to content
MangoDock

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

    ExploreDocsPricing
    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.

    ExploreDocsPricing
    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.

    ExploreDocsPricing
    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

    Dashboard

    One card per Docker host, and the switch between them.

    On each card

    • Name and the connection target it was added with — a socket path, a host and port, or an SSH target.
    • State counts across running, stopped, paused, restarting and unhealthy, plus the total.
    • A health banner that names the problem when there is one, rather than only a number.
    • CPU and memory gauges, and a history sparkline for both, so a spike is distinguishable from a level.
    • Object counts for images, stacks, volumes and networks — the stacks count broken down into running, stopped and partial.
    • A disk usage donut split across images, containers and volumes, with the total.
    • The recent events feed with relative timestamps, and the top containers by CPU with their memory alongside.

    Across the top

    • The host switcher, then facts about whichever host is selected: OS and architecture, Docker version, connection kind, cores, memory, disk and uptime.
    • A clock, a live-connection indicator, global search on Ctrl or Cmd + K, and the theme toggle.
    • The connection-kind chip is the one piece of chrome that is not cosmetic: it distinguishes a socket from SSH-with-socket and SSH-with-exec, and the last of those cannot do anything live.

    Header actions

    • Add a host, import one, change the card layout, or refresh.
    • Four layout densities, from a single summary line up to the full card described above.

    Air-gapped

    • Everything on this page is polled from the daemons you added. None of it reaches outside the network.
    ← Updating and uninstallingContainers →