fshy

fshy / Egress and tunnels

OpenTunnel

github.com · Egress and tunnels · 1 record · JSON

OpenTunnel Egress and tunnels

fails: egressanonymousno cardR

github.com/anomalyco/opentunnel · hosted blind tls tunnel (tcp 443, tls clienthello only) · egress/opentunnel · JSON · compare

Free tiereach client gets a unique <id>.opentunnel.xyz subdomain and TLS is terminated locally
unit none; metered on none
PriceUSD 0
Per-object capnot applicable
Retentionnot applicable
EgressNo byte allowance or price is published in the README.; ingress: http-only
free_allowance: none published
Identityanonymous a client claims a route by hostname; no account is described in the README.
Bindingnone 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.
Interfacecli npm client.
Toolingvendor client (TypeScript).
Composes withWeb ingress for a free VM, with client-side TLS termination.
ReliabilityDepends on a Cloudflare TCP Workers beta and a temporary AWS relay.
NotesBlind TLS relay on Cloudflare Workers with an AWS relay for inbound TCP. Interesting shape, no UDP.
Evidence rungreported The hosted service is young (MIT declared, no LICENSE file); a published quota would sharpen the binding.
Checked2026-10-23 (live); stale on 2026-11-06
Parsed numbers
  • $.price_per_tb_month price-per-tb USD0.0 TB / month
Evidence (1)
datesourcewhat it proved
2026-10-23github.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.stated not-applicable
  • $.retention.stated not-applicable