OpenTunnel
github.com · Egress and tunnels · 1 record · JSON
OpenTunnel Egress and tunnels
fails: egressanonymousno cardR
| Free tier | each client gets a unique <id>.opentunnel.xyz subdomain and TLS is terminated locally unit none; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte allowance or price is published in the README.; ingress: http-only free_allowance: none published |
| Identity | anonymous a client claims a route by hostname; no account is described in the README. |
| Binding | none No quota is published, so the byte wall is unknown; the hard wall is that the relay reads only the TLS ClientHello and routes by SNI, so only TLS-wrapped traffic reaches the client. No UDP. |
| Interface | cli npm client. |
| Tooling | vendor client (TypeScript). |
| Composes with | Web ingress for a free VM, with client-side TLS termination. |
| Reliability | Depends on a Cloudflare TCP Workers beta and a temporary AWS relay. |
| Notes | Blind TLS relay on Cloudflare Workers with an AWS relay for inbound TCP. Interesting shape, no UDP. |
| Evidence rung | reported The hosted service is young (MIT declared, no LICENSE file); a published quota would sharpen the binding. |
| Checked | 2026-10-23 (live); stale on 2026-11-06 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | github.com/anomalyco/opentunnel | 'It accepts public TCP on 443 and reads only the TLS ClientHello. A tunnel hostname is carried, still encrypted, over the tunnel bridge WebSocket' |
More fields (7)
{
"wg_path": "none",
"wg_detail": "",
"ingress": "http-only",
"volume_tib_month": null,
"volume_stated": "No byte allowance or price is published in the README.",
"bytes_transit": "yes",
"transit_note": ""
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable