Mullgate
Operator docs for installing, setting up, using, and troubleshooting Mullgate.
Mullgate is a CLI-first proxy and gateway product for operators who need explicit, inspectable routing behavior. It exposes multiple local proxy entrypoints, keeps hostname-to-route mapping truthful, and documents the setup, proxy, and config workflows directly.
This site is the operator-facing guide to installing Mullgate, configuring routes, using the CLI, and troubleshooting real setups.
What Mullgate is for
Mullgate is built around a few stable ideas:
- expose local proxy endpoints concurrently
- choose routes by stable hostnames or direct bind IPs
- support SOCKS5, HTTP, and HTTPS-capable proxy surfaces
- scale many routed exits from one shared Mullvad device
- keep host routing unchanged instead of acting like a full-device VPN
- make runtime and diagnostic state visible through the CLI
- preserve truthful documentation for platform support and routing behavior
Start here
Installation
Install Mullgate and verify the CLI on your platform.
Quickstart
Follow the fastest path through setup, validation, and first use.
Usage
Read the full setup, exposure, export, and relay workflow.
Troubleshooting
Diagnose hostname, exposure, runtime, and relay issues.
Documentation map
Getting started
Guides
Architecture
Reference
Other
Suggested reading order
If you are new to Mullgate, start with the operator path:
Read the architecture pages after that if you want the design background.
What to expect from the site
The docs emphasize:
- accurate platform caveats
- practical setup examples
- clear exposure and hostname guidance
- runtime lifecycle and validation workflows
- a transparent explanation of the shared-entry scaling model and the redesign that produced it