Home / Egress and tunnels
LetsTunnel
letstunnel.com/Relay (hosted, HTTPS tunnel, QUIC)egress/letstunnelJSONcomparereport an errorprovider JSON
- Free allowance
- Free for developers with no account, with public HTTPS URLs, QUIC on UDP 8443 and a desktop app.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not stated
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-25checked 2026-11-10 (live); stale on 2026-11-25
| Free tier | Free for developers with no account, with public HTTPS URLs, QUIC on UDP 8443 and a desktop app. On 2026-11-05 the relay presented a self-signed certificate and no tunnel could be established. unit none; metered on none |
|---|
| Price | none stated |
|---|
| Binding | none nothing is reachable to bind on: the relay presented a self-signed certificate on 2026-11-05, so a client that verifies TLS cannot connect. |
|---|
| Identity | anonymous no account is claimed: the page says 'Free for developers', and no signup was attempted |
|---|
| Egress | no byte quota is published; the relay was unreachable with a valid certificate on 2026-11-05 |
|---|
| Per-object cap | not applicable: a tunnel, not an object |
|---|
| Retention | not applicable: a live tunnel |
|---|
| Interface | cli the letstunnel CLI starts a tunnel and prints a public https://<name>.letstunnel.com URL; the documented relay port is UDP 8443 over QUIC |
|---|
| Tooling | the letstunnel npm CLI, a node wrapper around a Rust client |
|---|
| Composes with | nothing chains until the relay certificate is fixed; the authless claim looks genuine and the CLI loads |
|---|
| Reliability | the relay presented a self-signed certificate on 2026-11-05, so a client that verifies TLS cannot connect; the documented relay port 8443 was unreachable |
|---|
| Notes | The authless claim looks genuine and the CLI loads, but the relay presented a self-signed certificate on 2026-11-05, so no tunnel could be established. Retest when the certificate is fixed. |
|---|
| Evidence note | reported the free and no-account claims are read from the vendor page; the certificate failure is a sandbox observation, so the record is reported |
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-11-10 | letstunnel.com/ | a user is free for developers |
| 2026-11-05 | probe: https://relay.letstunnel.com:443 | part of the text of Free tier, above |