Defguard
defguard.net · Egress and tunnels · 1 record · JSON
Defguard Egress and tunnels
fails: egressanonymousno cardDrequest-rate
| Free tier | Open Source: 'Always free', 'Unlimited users and locations - core features.' Business: 'free up to 10 users and 1 location.' unit users; metered on identity-count |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte allowance anywhere in the plan table; the plans meter users and locations.; ingress: none free_allowance: none published |
| Identity | anonymous self-hosted: the Open Source plan needs no vendor account; the Business plan is a hosted or licensed deployment with its own admin |
| Limits |
|
| Binding | request-rate The published caps are users and locations, for which the vocabulary has no token; request-rate is the nearest. Nothing counts bytes, and there is no public listener to spend them through. |
| Interface | cli web admin plus the desktop client |
| Tooling | defguard server, defguard desktop client, standard WireGuard configs |
| Composes with | a control plane for a user's own WireGuard mesh; it composes with a public ingress on the same VPS |
| Reliability | the Open Source plan is self-run, so uptime and key rotation are local work |
| Notes | The most WireGuard-native name and the least useful for it: it hands out .conf files for a private VPN, and its own gateway is not a public reverse proxy. Worth recording because a reader searching for 'WireGuard' will land here. |
| Evidence rung | documented Reading the gateway documentation would establish whether Defguard's own gateway can bind a public port; the VPN-server model suggests not. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | defguard.net/pricing/ | Open Source is 'Always free' with 'Unlimited users and locations'; Business is 'free up to 10 users and 1 location' |
| 2026-10-23 | defguard.net/pricing/ | 'Zero-touch Desktop Client Provisioning' and 'Client configuration update based on tokens', the mechanism that issues WireGuard configs |
More fields (7)
{
"wg_path": "native-conf",
"wg_detail": "Defguard provisions the client's tunnel: 'Zero-touch Desktop Client Provisioning' and 'Client configuration update based on tokens'. The product is a WireGuard control plane, which is the one place where a standard client config is the deliverable.",
"ingress": "none",
"volume_tib_month": null,
"volume_stated": "No byte allowance anywhere in the plan table; the plans meter users and locations.",
"bytes_transit": "overlay-only",
"transit_note": "peers reach each other over the WireGuard tunnels Defguard configures; the server sees handshakes, not payload"
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable