Home / Egress and tunnels
tunnel.pyjam.as
tunnel.pyjam.as/HTTP tunnel over a wireguard link issued by curlegress/tunnel-pyjam-asJSONcomparereport an errorprovider JSON
- Free allowance
- SSL-terminated HTTP tunnels to your local machine - no custom software required, thanks to Wireguard
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not statedsee Price below
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented1 source; 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 | SSL-terminated HTTP tunnels to your local machine - no custom software required, thanks to Wireguard unit none; metered on none |
|---|
| Price | USD 0 |
|---|
| Binding | none Nothing is published, so the byte wall is unknown, and the service is a hobby endpoint whose capacity is one host. Ingress is HTTPS only, so no UDP and no raw TCP reaches a user: the WireGuard link is how the vendor carries the HTTP tunnel, not a port a user can serve on. |
|---|
| Identity | anonymous no account: the curl request is the whole signup. |
|---|
| Egress | No allowance or price is published; the page is four lines long.; ingress: http-only free allowance: none published |
|---|
| Interface | cli curl plus wg-quick |
|---|
| Tooling | curl and wg-quick. |
|---|
| Composes with | Carries HTTP only; the WG link is the transport, not the ingress. |
|---|
| Reliability | One community host with no stated capacity or SLA. |
|---|
| Notes | The most interesting no-account entry in the sweep: a WireGuard config with zero registration, but the far side terminates HTTPS so the WireGuard link carries only HTTP. The same request shape would not forward a raw UDP port. |
|---|
| Evidence note | documented The page sets no quota, so only a live transfer shows the real tolerance; the risk is that a shared community endpoint disappears. |
|---|
| Parsed numbers | |
|---|
Evidence 1
More fields 5
| wg path | registration-api |
|---|
| wg detail | The registration endpoint is the URL itself: 'curl https://tunnel.pyjam.as/8080 > tunnel.conf && wg-quick up ./tunnel.conf'. The port in the path is the local service, and the response is a wg-quick config. |
|---|
| ingress | http-only |
|---|
| volume stated | No allowance or price is published; the page is four lines long. |
|---|
| bytes transit | yes |
|---|
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