Skip to content
MangoWiFi

  • 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

    • Criteria tests

    The conventional per-metric suite that runs Agent-side.

    Criteria — the conventional suite, grouped the way commercial test plans group it.

    These are the rows an AP is normally measured on, grouped the way commercial suites group them. They run from the Agent, so traffic crosses the air and then the wire to the LAN receiver.

    • Basic — Association, authentication, DHCP, link rate, ping RTT parsed into p50 and p95, and a lenient wire-smoke latency probe.
    • TCP — Goodput up, down and bidirectional, each also at four concurrent sessions.
    • UDP — Throughput and loss, including the high-load profile the Wi-Fi 8 runners borrow as their concurrent load.
    • RFC 2544 — Forwarding rate, frame loss, back-to-back and latency.
    • Range — Uplink, downlink, an MCS sweep, and throughput against range.
    • Capacity — Association bursts, interleaved clients and scalability.
    • Application — HTTP GET, G.711 voice, and constant- and variable-bitrate video.
    • Compatibility — Mixed-generation clients and legacy coexistence.

    Ping RTT parsing differs by platform: 10 pings at one-second spacing on Windows, 30 at 100 ms on Linux. The percentiles are computed from whichever set the platform produced.

    ← Wi-Fi 8 (802.11bn D2.0)Reading a result →