Self-hosted, zero-trust network access — the convenience of modern cloud access tools, owned end to end by you. Deployable inside a fully air-gapped enclave or across the open internet, from one codebase, on a WireGuard data plane.
No mystery boxes. This is what DragonGate is made of.
| Architecture | Four cooperating services + admin CLI: Controller (source of truth: users, devices, resources, policies, key distribution), Connector (outbound-only gateway inside each private segment), Client (per-device agent, split-tunnel routing), Relay (NAT-traversal broker that only ever sees ciphertext), and dgctl for administration. |
|---|---|
| Language | 100% memory-safe Rust — every crate compiled with #![forbid(unsafe_code)]. Whole classes of exploits (buffer overflows, use-after-free) are ruled out at compile time. |
| Data plane | WireGuard tunnel: X25519 key exchange, ChaCha20-Poly1305 authenticated encryption, BLAKE2s hashing. |
| Control plane | Mutual TLS 1.3 (ECDHE + AEAD) — both sides authenticate with certificates on every connection. No passwords on the wire, ever. |
| PKI | Built-in internal certificate authority (ECDSA P-256), designed for an HSM-backed root. Your infrastructure, your CA — no third-party certificate dependency required. |
| Crypto backends | Swappable at build time: ring (default) or AWS-LC in FIPS mode for deployments that require a FIPS 140-3 validated module. The FIPS profile compiles and passes the full control-plane test suite. (Module validation itself is an external certification process.) |
| Authentication | PIV/CAC smart cards and FIDO2 hardware keys, against a local directory (air-gapped) or your OIDC/SAML identity provider (networked). |
| Zero-trust model | Deny by default. Every resource requires an explicit grant; grants are short-lived and device-bound; revocation is immediate. Being "on the network" grants exactly nothing. |
| Audit | Full audit log of grants and access with a cryptographically signed head (ECDSA P-256 / SHA-256) — tamper-evident by design. |
| Deployment profiles | Enclave: fully air-gapped — local auth, controller-as-CA, signed offline update bundles, zero external dependencies, zero telemetry. Networked: internet-reachable with relays and optional IdP integration. Same codebase, one build. |
Designed against real adversaries, not marketing ones.