Skip to content

Introduction

The Gateway is a single Go daemon (gatewayd) plus a React control plane that runs every plane of your network from one place:

  • the firewall (nftables, atomic table replacement)
  • a recursive DNS resolver with per-device filtering and rewrites
  • WireGuard / OpenVPN tunnels with fwmark-based policy routing
  • a traffic-splitting engine with six configurable privacy levels
  • bridge proxies for censorship resistance (TLS by default, obfs4 for DPI-heavy networks)
  • a Tailscale or self-hosted Headscale mesh
  • per-device, per-domain routing policies with exceptions and TTLs
  • a reference-counted, fail-closed kill-switch
  • federation across multiple gateway nodes

The current application release is v2.19.0 for Linux amd64 and arm64. It includes server management for relays, bridges, Splitting services and gateway nodes, plus a shared release cache and self-update workflow. Management is admin-only and disabled by default. v2.19.0 sends the gateway’s own downloads through a tunnel by default, removes public fallback resolvers, and adds an opt-in new-connections-only Splitting rotation. These defaults change on upgrade; nodes without a VPN policy must explicitly allow direct downloads or use uploaded releases. Release-signing public keys are built in from v2.18.1: signed releases can be authenticated by the gateway and bootstrap. Automatic updates remain opt-in. Upgrading from v2.18.0 requires manual archive acceptance or the installer. See Updates and release trust and release evidence.

It targets two deployment shapes:

  • Raspberry Pi as a home / travel / small-office gateway with WiFi AP, DHCP, captive-portal detection and SD-card hardening.
  • Linux VPS (amd64 or arm64) as a remote node, a bridge, or a federation peer.

The Gateway is built for operators: people who already understand nftables, WireGuard and policy routing, and want a coherent control plane on top instead of a folder of bash scripts.

It is a good fit if you:

  • want per-device routing (e.g. “laptop through tunnel A, work phone through bridge B, IoT direct”)
  • need a fail-closed kill-switch that survives tunnel restarts without leaking
  • run multiple VPN exits and want to split connections across them
  • are deploying in censored environments and need pluggable transports
  • operate two or more gateways and want them to share state
  • prefer one binary, one SQLite file and one REST API over a microservice zoo

It is not a good fit if you:

  • want a one-click consumer VPN appliance
  • need Windows or macOS as a deployment target (Linux only)
  • want a fully open-source project (The Gateway is private / proprietary)
┌─────────────────┐
Web UI / API ─────►│ gatewayd │
│ (Go daemon) │
gwctl CLI ─────►│ │
│ SQLite store │
└────────┬────────┘
│
┌────────────────┼────────────────┐
▼ ▼ ▼
nftables / DNS plane Transport
iptables (resolver + (WG, OVPN,
dataplane filtering) SOCKS5)
│ │
└──────────────┬──────────────────┘
▼
Devices (LAN /
WiFi / Mesh)

The daemon owns every kernel-level resource it touches (nftables tables, ip rule, ip route, network namespaces). A reconciler scans this state once a minute (configurable, minimum 5 s) and re-applies anything that drifted, so a misbehaving sibling process or an out-of-band edit doesn’t silently break your policy.