Home / Egress and tunnels
wireguard-go
github.com/WireGuard/wireguard-goTool (wireguard transport)egress/wireguard-goJSONcomparereport an errorprovider JSON
- Free allowance
- No service and no account; the reference userspace implementation
- Verdict
- self-hosted, last resortverdict fails-egress: data cannot be read back out at a usable rate or price. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- not statedsee Price below
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | no service and no account; the reference userspace implementation unit none; metered on none |
|---|
| Price | USD 0 |
|---|
| Binding | none it creates a TUN interface and speaks UDP; a UDP block stops it, so it adds no egress path |
|---|
| Identity | anonymous no account |
|---|
| Egress | not applicable; the software states no volume; ingress: none free allowance: none published |
|---|
| Interface | cli wireguard-go wg0, configured with wg(8) |
|---|
| Tooling | go build; wg and wg-quick for configuration |
|---|
| Composes with | the substrate for the WebSocket forks; on its own it composes only with a peer that accepts UDP. |
|---|
| Reliability | upstream mirror lags git.zx2c4.com; the Linux kernel module is the faster path where it exists |
|---|
| Notes | As shipped it is UDP only, so it is not a wrapper. It is also the tool that makes a standard .conf usable on a platform with no kernel WireGuard, which is the case for Windows and for containers on hosts without the module. |
|---|
| Evidence note | documented the verdict concerns egress only; this is the implementation every WebSocket fork starts from |
|---|
| Parsed numbers | |
|---|
Evidence 3
More fields 9
| wg path | native-conf |
|---|
| wg detail | "With wireguard-go, instead simply run: wireguard-go wg0 ... When an interface is running, you may use wg(8) to configure it", so the standard configuration applies unchanged |
|---|
| ingress | none |
|---|
| volume stated | not applicable; the software states no volume |
|---|
| bytes transit | yes |
|---|
| transit note | carries the tunnel over UDP to the configured endpoint |
|---|
| hosting requirement | none beyond the device; needs a reachable UDP peer |
|---|
| last release | no GitHub release objects; last push 2026-10-06 |
|---|
| stars | 4465 |
|---|
Unknown values 2
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer