JANUS Documentation¶
Secure Access. Your Network. Your Rules. — by Korves.Net
JANUS is a Git-backed, API-first policy and routing control plane for WireGuard-based remote access. It lets an operator grant access to their own network precisely — per user, per device, per resource — and deny everything else, without exposing anything that was not explicitly permitted.
What JANUS does¶
A client enrols with its own WireGuard key and establishes a real tunnel to a JANUS Gateway. The Gateway forwards the client's traffic only to the resources that policy permits; everything else is dropped. Access decisions come from declarative configuration held in Git, which is compiled into a per-Gateway desired state and enforced on the Gateway in the data plane.
The key properties that follow from that design:
- Declarative. The desired state of the network is authored as configuration, versioned in Git, and reconciled — not clicked into place.
- API-first. The WebUI is an API client; every operation is available through the management API.
- Fail-closed. Forwarded traffic that no policy authorises is dropped.
- Multi-tenant. Tenants, Deployments and Gateway nodes are separate concepts; a physical Gateway node can serve several isolated Deployments.
- Distributed. One Deployment can span several Gateway nodes over a Deployment-scoped fabric.
How to read this site¶
| I want to… | Start here |
|---|---|
| Understand what JANUS is | Getting started |
| Install a Controller or a Gateway | Installation |
| Understand the architecture | Architecture overview |
| Configure policies | Configuration |
| Run and operate JANUS | Operations |
| Fix a problem | Troubleshooting |
| Look up a command or an API call | Reference |
| See what changed in a release | Releases |
Status¶
This documentation describes the current JANUS release. The documentation version tracks the JANUS release version; see Releases for how versions are mapped to documentation.