Home / Egress and tunnels
wireguard-ws
github.com/n0madic/wireguard-wsTool (wireguard transport)egress/wireguard-wsJSONcomparereport an errorprovider JSON
- Free allowance
- No service and no account; a fork of wireguard-go with a WebSocket transport
- Verdict
- self-hosted, last resortverdict paid-only: no free allowance; listed for its price. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- no price 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; a fork of wireguard-go with a WebSocket transport unit none; metered on none |
|---|
| Price | USD 0 |
|---|
| Binding | none both ends must run the fork and the server needs a TLS certificate; there is no hosted service to attach to |
|---|
| Identity | anonymous no account |
|---|
| Egress | not applicable; the software states no volume; ingress: tcp free allowance: none published |
|---|
| Interface | cli wireguard-ws wg0 with WG_WS=1 |
|---|
| Tooling | go build; TLS certificates for the server side |
|---|
| Composes with | composes with any host where the operator can run the forked binary at both ends; no CDN is documented as tested. |
|---|
| Reliability | client defaults to skipping certificate verification (WG_WS_INSECURE=1); no releases, one author |
|---|
| Notes | The interesting property is that the transport change happens inside the WireGuard implementation, so the interface and the configuration stay standard: this is the closest thing to a wrapper that a .conf-only router could accept, if the router ran the fork. It does not, so in practice the fork must run on a Linux host at both ends. Zero stars and no releases make it a reference for the approach rather than a deployment. |
|---|
| Evidence note | documented the repository has no releases and no stars, so the rung cannot rise without a build and a measured run |
|---|
| Parsed numbers | - has-free-tier 0
- price USD 0
|
|---|
Evidence 3
More fields 9
| wg path | native-conf |
|---|
| wg detail | "Fully compatible with standard wg and wg-quick tools"; WG_WS=1 switches the transport and the peer endpoint stays host:port |
|---|
| ingress | tcp |
|---|
| volume stated | not applicable; the software states no volume |
|---|
| bytes transit | yes |
|---|
| transit note | over a websocket between two hosts running the fork |
|---|
| hosting requirement | two hosts running the fork, the server one with a TLS certificate |
|---|
| last release | none; last push 2026-06-12 |
|---|
| stars | 0 |
|---|
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