rustunnel
rustunnel.com · Egress and tunnels · 1 record · JSON
rustunnel Egress and tunnels
paidemailno cardDvolume-quota
| 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 |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No free byte allowance is published anywhere read today. The managed service is 'Pay-as-you-go from $3/mo - idle time always free'; ingress: udp free_allowance: none published |
| Identity | email 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 |
| Limits |
|
| Binding | volume-quota A metered service with no published free allowance binds on bytes by construction: at one TiB a month the client is a paying customer. Self-hosting moves the cost to a VM, which is a compute-lane answer rather than an egress answer. |
| Interface | cli, rest 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 | Read because the brief names it. 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 rung | documented 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. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | www.rustunnel.com/docs/reference/udp-tunnels.md | UDP tunnels exist, the public port comes from a dedicated UDP range, sessions are reaped after 60 seconds of inactivity |
| 2026-10-23 | www.rustunnel.com/ | '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' |
| 2026-10-23 | www.rustunnel.com/docs/quickstart.md | 'Create a free account' and 'Access to the hosted service requires an auth token'; no allowance stated |
More fields (7)
{
"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_tib_month": null,
"volume_stated": "No free byte allowance is published anywhere read today. 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"
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable