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

    • Overview

    What the thing is, and the shape of a run.

    Overview. Both radios are chipped MOCK because no MT7925 is present — the app says so itself rather than pretending.

    MangoWiFi tests an access point, not a client. It drives real traffic across the AP from a station-side box and measures what comes back, then scores the result against thresholds that come from Wi-Fi Alliance UHR targets where those exist.

    The three machines

    • Console — The Tauri 2 desktop UI. Orchestrates the run, fires the latency probe, renders and exports results. Normally wired to the AP's LAN side.
    • Agent — Headless, on the station side, associated to the AP over the air. Runs a WebSocket server, echoes UDP, and runs iperf3 when asked.
    • LAN receiver — A plain box on the AP's wired side running iperf3 -s. Its only job is to be the far end of throughput traffic so the path is air-then-copper.

    Why the topology is the measurement

    The probe leaves the Console, crosses the AP under test, is echoed by the Agent and crosses back. That round trip is the number. Run Console and Agent on one machine and the same code measures loopback — useful for verifying the wiring, meaningless as a Wi-Fi result.

    On Windows the app runs in preview mode: radios report as mock and tests stage without executing. Real measurement needs Linux on the Agent.

    Hardware setup →