You shouldn’t have to edit config files just to expose a service.
bGate is a self-hosted manager for Caddy, designed to simplify how you configure reverse proxies, domains, and routing.
It gives you a clean interface for managing services without touching Caddyfiles, while still keeping the flexibility and power of Caddy underneath.
What it does
- Manage domains and routes
- Configure reverse proxies without writing Caddyfiles
- Handle TLS automatically via Caddy
- Organize services in one place
- Act as an entry point for your infrastructure
Why it exists
Most reverse proxy setups start simple, then slowly turn into a mess of config files.
bGate exists to keep things structured without removing control.
It’s built for people who:
- run multiple services
- self-host their infrastructure
- don’t want to fight configuration every time they deploy something
How it works
bGate sits on top of Caddy and acts as a control layer.
Instead of manually editing configs, you define routes and services through the UI, and bGate handles the rest.
Under the hood:
- Caddy handles TLS and routing
- bGate manages configuration state
- services are mapped to domains and ports
Current status
bGate is live and actively used.
It continues to evolve as new use cases appear, especially around managing more complex setups and integrations with other parts of the ecosystem.
Ecosystem
bGate is part of a growing set of tools:
- bLink (in progress) → WireGuard-based network management
- bLock (planned) → identity and access management
Over time, these tools are designed to work together:
- bGate handles exposure
- bLink handles connectivity
- bLock handles access