Home / Egress and tunnels
Loophole
loophole.cloud/docs/faqTunnel (hosted, HTTP only)egress/loophole-cloudJSONcomparereport an errorprovider JSON
- Free allowance
- We do not enforce any limitations on concurrent connections, number of requests or bandwidth.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | We do not enforce any limitations on concurrent connections, number of requests or bandwidth. unit unlimited; metered on none |
|---|
| Price | USD 0 |
|---|
| Binding | none No quantity binds because the proxy speaks HTTP only; at 1 TiB the first failure is that there is nothing to forward. |
|---|
| Identity | email a sign-up account and an authtoken: 'you need to sign up for an account' |
|---|
| Egress | no quota: 'We do not enforce any limitations on concurrent connections, number of requests or bandwidth. Neither in the cli nor in our proxy servers.'; ingress: http-only free allowance: none published |
|---|
| Interface | cli loophole http 3000 -s name |
|---|
| Tooling | loophole CLI |
|---|
| Composes with | HTTP ingress only |
|---|
| Reliability | one small operator; no published uptime |
|---|
| Notes | A generous free service disqualified by protocol alone, which is the classic case the memo's tooling rule warns against confusing with a capacity judgement. |
|---|
| Evidence note | documented The vendor states the protocol limit twice, in the FAQ and in a repository discussion. Nothing would raise it. |
|---|
| Parsed numbers | - has-free-tier 1
- price USD 0
|
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-23 | loophole.cloud/docs/faq | 'Loophole currently supports http/https connections only', and the no-limits statement |
| 2026-10-23 | loophole.cloud/ | 'Instantly create a public HTTPS url for a website running locally' |
More fields 6
| wg path | none |
|---|
| wg detail | 'Loophole currently supports http/https connections only.' There is no TCP path and no UDP path. |
|---|
| ingress | http-only |
|---|
| volume stated | no quota: 'We do not enforce any limitations on concurrent connections, number of requests or bandwidth. Neither in the cli nor in our proxy servers.' |
|---|
| bytes transit | yes |
|---|
| transit note | the Loophole proxy carries the HTTPS traffic |
|---|
Unknown values 2
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer