# rustunnel

> rustunnel.com | Egress and tunnels; 1 record: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/rustunnel/ | JSON https://fshy.ajam.dev/api/v1/entity/rustunnel.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## rustunnel

- `egress/rustunnel` | paid-only | evidence documented | binding volume-quota | category udp port forward (self-hostable server, managed cloud) | tier free
- needs card no, phone no, ID no, institution no | verified 2026-10-23 (live) | stale on 2026-11-23
- url https://www.rustunnel.com/docs/reference/udp-tunnels.md
- price USD 0
- free tier: Create a free account and generate an auth token; self-hosting is free under AGPL. The managed cloud is pay-as-you-go from USD 3/month. | unit: none | metered on: unstated | read on: 2026-10-23 | source: [1]
- per-object cap: not applicable | source: [2]
- retention: not applicable | source: [2]
- egress: No free byte allowance is published anywhere read. The managed service is 'Pay-as-you-go from $3/mo - idle time always free'; ingress: udp | metered: no | free allowance: none published | source: [2]
- identity: email | detail: a free account and a generated auth token: 'Access to the hosted service requires an auth token. Create a free account and generate one yourself.' https://www.rustunnel.com/docs/quickstart.md | country: None
- interface: cli, rest
- limits:
  - volume-quota (binding): no free byte allowance published; the managed cloud is metered and billed from USD 3/month [3]
- binding note: A metered service with no published free allowance binds on bytes by construction: at one TiB a month a user is a paying customer. Self-hosting moves the cost to a VM, which is a compute-lane answer rather than an egress answer.
- interface detail: mytunnel client, a live dashboard, Prometheus metrics and an audit log
- tooling: mytunnel client from brew or a binary, self-hostable server in Rust
- composes with: self-hosting on a free VM turns this into a free UDP relay; the managed cloud does not
- reliability: sessions are reaped after 60 seconds of inactivity, which suits WireGuard keepalive but means an idle peer is torn down
- notes: The UDP implementation is the best documented of any free-or-cheap tunnel found, and it is the wrong side of a paywall for a user. There is no pricing page: /pricing and /pricing.html both 404, so the only price statement is the homepage sentence.
- evidence note: The UDP mechanics and the pay-as-you-go price are read from the vendor's own pages. The openness is the free-account sentence with no allowance behind it. Raise by signing up free, running mytunnel udp against a listener, and reading whether a port is allocated and whether it survives a restart.
- self hosted: no
- extras:
  - wg_path: unknown
  - wg_detail: UDP tunnels are real and documented: 'rustunnel UDP tunnels forward datagrams from a public port on the tunnel server to a local UDP service', with 'Public port - allocated from a dedicated UDP port range on the server' and a 60-second session idle timeout. Whether a free hosted account gets a port, and whether the port is fixed, is not stated. https://www.rustunnel.com/docs/reference/udp-tunnels.md
  - ingress: udp
  - volume_stated: No free byte allowance is published anywhere read. The managed service is 'Pay-as-you-go from $3/mo - idle time always free'.
  - bytes_transit: yes
  - transit_note: the managed relay carries the datagrams, or the self-hosted server does
- evidence:
  - [2] 2026-10-23: UDP tunnels exist, the public port comes from a dedicated UDP range, sessions are reaped after 60 seconds of inactivity
  - [3] 2026-10-23: 'Pay-as-you-go from $3/mo - idle time always free. Or self-host free under AGPL', plus 'Start free' and 'free self-hosting under AGPL'
  - [1] 2026-10-23: 'Create a free account' and 'Access to the hosted service requires an auth token'; no allowance stated
- sources:
  - [1] https://www.rustunnel.com/docs/quickstart.md
  - [2] https://www.rustunnel.com/docs/reference/udp-tunnels.md
  - [3] https://www.rustunnel.com/