Mullgate
Comprehensive documentation for Mullgate, a CLI-first proxy and multi-exit gateway.
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 both the current runtime model and the proposed multi-exit architecture.
This Fumadocs site turns the repository's longer-form notes into a browsable documentation set with clear navigation, cross-links, and operator-focused guidance.
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
- 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 release operations
Start here
Installation
Prepare the docs app and local working environment.
Quickstart
Learn the fastest path through setup, validation, and routing.
Usage
Read the full usage guide migrated from the repository source.
Architecture
Understand the runtime model, bind IP design, and multi-exit roadmap.
Documentation map
Getting started
Guides
Architecture
Operations
Reference
Other
How the docs are organized
The most important source documents in the repository are:
usage.mdpublishing.mdmulti-exit-architecture-spec.md
Those root docs now appear in the site as polished, structured pages. Supporting pages split out the core operator workflows into smaller sections that are easier to browse and maintain.
Suggested reading order
If you are new to Mullgate, start with:
- Quickstart
- Usage
- Setup and Exposure
- Architecture Overview
- Current Runtime Model
- Multi-exit Architecture Spec
- Publishing
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
- release and publishing expectations
- a transparent explanation of the current scaling limit and the proposed next step