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

    • Advanced

    Schedules

    Redeploys that happen without anyone asking.

    What can be scheduled

    • A saved stack, redeployed on a cron expression by a background loop with real graceful shutdown.
    • A git-linked stack, redeployed when its repository moves.
    • Filters by host, by type and by status, with the last run and its outcome on each row.
    • A failed run is called out on the row rather than left for you to find.

    GitOps

    • Deploys run git as a real subprocess against a real repository.
    • A private repository's access token is injected per request and never written to disk.
    • An inbound webhook redeploys on push, authenticated by a bearer token carried in its own URL rather than by a session.

    When they fire

    • Schedules only fire while MangoDock is running.
    • A run missed because it was closed fires once on the next launch, rather than replaying every window that was skipped.

    Air-gapped

    • A scheduled redeploy needs a registry to pull from — your mirror serves that.
    • A git-linked schedule needs a git host inside the enclave; a bare repository on a reachable machine is enough.
    • Webhooks are inbound, so they work without any outbound route at all.
    ← SwarmBackups →