Skip to content
MangoSSH

  • 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

    • Limits & Troubleshooting

    Current, deliberate constraints, and where to look when something is wrong.

    Known limitations

    • PKCS#11 hardware-token authentication is RSA-only in the current release; ECDSA tokens are not yet supported.
    • Windows Hello SSH keys use RSA 2048 on Windows; Secure Enclave keys on macOS use ECDSA P-256.
    • Multi-monitor RDP is explicitly experimental and may behave inconsistently across setups.
    • MangoSSH Direct is Windows-host-only and captures the interactive desktop session, so it cannot reach a locked or logged-out machine.

    Common symptoms

    • A saved host disappeared — Almost always a different active profile, or a host-visibility group filter.
    • Permission denied (publickey) — Wrong key or passphrase, or the public key is not in the server's authorized_keys.
    • RDP connects to a black screen — Usually an NLA or Domain field mismatch.
    • An unexpected host-key prompt — Expected on a genuinely new host; worth investigating on one you have used before.
    • Locked out of a vault — Each tier's master password, device keys and recovery code are non-recoverable by design.

    The full symptom index, with the cause and fix for each, is in the Troubleshooting chapter.

    Full detail

    Step-by-step instructions, how to check each one worked, and what to do when it did not.

    ← Settings & Appearance