tunr
tunr.sh · Egress and tunnels · 1 record · JSON
tunr Egress and tunnels
fails: egressemailno cardDwrite-gated
| Free tier | Open-source CLI - Free tunnels - 3 free apps. The 3-second tunnel that started it all - still free, still first-class. HTTPS, WebSocket, TCP, UDP, TLS. unit none; metered on unstated |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte allowance is published. The deploy path caps the compressed upload at 50 MB, which is a deploy limit and not a tunnel allowance.; ingress: http-only free_allowance: none published |
| Identity | email Deploying an app needs a dashboard account at app.tunr.sh; share tunnels appear usable from the CLI. The signup form was not read. |
| Limits | |
| Binding | write-gated UDP never reaches the wire: raw TCP and UDP are only framed onto a WebSocket, so a WireGuard client cannot dial it at all. That gate binds before any allowance. |
| Interface | cli, rest tunr share --port 3000, tunr deploy, and an MCP tool surface. |
| Tooling | brew install ahmetvural79/tap/tunr, or go install; an MCP server exposes tunr_deploy. |
| Composes with | Replaces a free VM for static demos; cannot carry a WireGuard handshake or a raw game protocol. |
| Reliability | Deployed apps sleep when idle and wake in about 150 ms; the tunnel tier is a marketing on-ramp to the deploy product, so it can be repriced. |
| Notes | Launched 2026-06-21 as a 3-second tunnel and has since pivoted to an app-deploy platform. The homepage claim of TCP and UDP support is true only in the WebSocket-framing sense, which the docs admit. |
| Evidence rung | documented A probe against a live tunnel would confirm the WebSocket-only framing; the docs state it plainly. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | tunr.sh/ | Free tunnels, 3 free apps, and the claim of HTTPS, WebSocket, TCP, UDP and TLS support. |
| 2026-10-23 | tunr.sh/docs.html | TCP, UDP and TLS are experimental and exposed only as a WebSocket stream; there is no raw TCP/UDP port on the relay yet. |
| 2026-06-21 | news.ycombinator.com/item?id=48623146 | Show HN launch date. |
More fields (7)
{
"wg_path": "none",
"wg_detail": "The relay has no raw UDP port yet: the docs say the relay exposes a raw tunnel only as a WebSocket stream at wss://<subdomain>.tunr.sh/tunnel/tcp (binary frames carry the bytes). There's no raw TCP/UDP port on the relay yet, so native clients like psql or ssh can't connect directly.",
"ingress": "http-only",
"volume_tib_month": null,
"volume_stated": "No byte allowance is published. The deploy path caps the compressed upload at 50 MB, which is a deploy limit and not a tunnel allowance.",
"bytes_transit": "yes",
"transit_note": "The tunr.sh edge relay carries the bytes over WebSocket."
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable