fshy

Home / Egress and tunnels

BastionRoute

bastionroute.io/UDP relayegress/bastionrouteJSONcomparereport an errorprovider JSON

Free allowance
A deliberately minimal forwarding fabric for WireGuard endpoints operating behind CGNAT, mobile networks and other NAT environments.
Verdict
self-hosted, last resortverdict qualifies-with-caveat: usable, with a named limit or an unprobed read path. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
volume-quotano published allowance; relay capacity unknown
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-07checked 2026-10-23 (live); stale on 2026-11-07
Free tierA deliberately minimal forwarding fabric for WireGuard endpoints operating behind CGNAT, mobile networks and other NAT environments. No price, plan or allowance is published; the repository is v0.1.0-alpha.
unit unlimited; metered on unstated
PriceUSD 0
Limits
  • volume-quota (binding) no published allowance; relay capacity unknown source
Bindingvolume-quota With no meter published and an alpha relay, the first failure at 1 TiB/month would be relay capacity or availability, not a stated cap.
Identityanonymous The README defines no authentication or accounts: BastionRoute intentionally does not define encryption, authentication, authorization, payload schemas, or application semantics.
EgressNo allowance is published. The relay is described as seeing connections, timing, traffic volume, frame sizes and connection state, but no cap is named.; ingress: udp
free allowance: none published
Interfacecli, unknown Relay plus shim binaries; the README describes a multi-shim architecture with no command reference.
ToolingShim plus relay from GitHub; no packaged client.
Composes withRun the relay on a free VM and the shim next to the WireGuard endpoint; the free VM gets a UDP path it would not otherwise have.
ReliabilityAlpha, single author, no authentication layer; the site itself says a hostile relay can drop, delay or disrupt traffic.
NotesThe most direct 2026 answer to the exact problem: a UDP relay that is explicitly designed to carry WireGuard from behind CGNAT. It is alpha, single-author, and has no hosted plan, so a user would run the relay on its own free VM.
Evidence notereported Only the project's own README, site and a Show HN post exist; no hosted signup and no pricing page were found. Running the relay would move this to measured.
Parsed numbers
  • has-free-tier 1
  • price USD 0
Evidence 3
datesourcewhat it proved
2026-10-23bastionroute.io/A forwarding fabric for WireGuard endpoints behind CGNAT: outbound WebSocket, opaque forwarding, WireGuard as the trust boundary; no price or plan.
2026-10-23github.com/klauscam/BastionRoute/blob/main/README.mdv0.1.0-alpha; relays UDP datagram streams between outbound-connected peers over WebSocket; defines no authentication.
2026-10-23news.ycombinator.com/item?id=48856767Show HN submission for an outbound-initiated WebSocket relay fabric for UDP; the item's own timestamp could not be retrieved from the HN API.
More fields 6
wg pathinside-udp
wg detailIts stated purpose is to carry WireGuard: the endpoint establishes an outbound WebSocket connection; the relay forwards opaque traffic; WireGuard remains the endpoint-to-endpoint security layer. The relay carries UDP datagrams as binary WebSocket frames.
ingressudp
volume statedNo allowance is published. The relay is described as seeing connections, timing, traffic volume, frame sizes and connection state, but no cap is named.
bytes transityes
transit noteA self-run or third-party relay forwards opaque frames between peers.
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