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

    • Automation

    Run saved scripts across hosts, chain steps into resumable runbooks, and let AI tools operate through MangoSSH under a policy gate.

    • Scripts — Saved scripts run against one host or many, in parallel — one connection per host. Each carries its own shell, wall and idle timeouts, tags, parameters prompted at run time, an optional hotkey, and files staged alongside the command body.
    • Runbooks — A graph of steps with dependencies and retries, stored in an event log. If MangoSSH closes mid-run, reopening it continues from the last completed step — where a script run would simply be lost.
    • MCP server — Lets external AI tools such as Claude Desktop or Cursor drive your SSH hosts. Every call passes a policy denylist; a refused call means the policy did its job.
    • AI Assistant — Reads a session's recent terminal output to help diagnose a problem. Entirely manual to invoke — likely secrets are redacted automatically and you approve the redacted text before anything is sent.

    Writing a script

    The command body runs on the host over SSH's exec channel. Hosts and an optional schedule sit on the right; a schedule only fires while MangoSSH is open, and a missed run fires once on next launch rather than replaying every window it skipped.

    Runbooks

    Each run is an event log rather than a transcript, so a step's status, its host and its collected output stay inspectable long after the run finished.

    Saved runbooks and a recent-runs log across all of them.
    One runbook's history, each run expanded into its step events.
    The output each step captured, newest run first.

    Step-by-step guides

    How to set each of these up, one task per page.

    Full detail

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

    ← Monitoring & AuditZero Trust & Relay →