Home / Egress and tunnels
Lantunnel
lantunnel.app/P2P mesh with an optional hosted control planeegress/lantunnelJSONcomparereport an errorprovider JSON
- Free allowance
- Lantunnel Client on each device.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not statedsee Price below
- Identity
- emailno 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 | Lantunnel Client on each device. Encrypted P2P paths, Relay fallback, and no router port forwarding. unit none; metered on none |
|---|
| Price | USD 0 |
|---|
| Binding | none No public URL and no metered quota: the mesh gives reachability between enrolled devices only, and 'Direct connectivity is not guaranteed'. |
|---|
| Identity | email clients are free; the hosted control plane at lantunnel.app is closed source and optional. |
|---|
| Egress | No allowance is published; Relay capacity is described as a shared resource rather than a quota.; ingress: none free allowance: none published |
|---|
| Interface | cli GUI clients plus a CLI. |
|---|
| Tooling | desktop and mobile clients. |
|---|
| Reliability | Relay capacity is shared; direct paths depend on NAT. |
|---|
| Notes | The hosted control plane does not carry a user's public ingress; that would need a Gateway a user runs. |
|---|
| Evidence note | documented A hosted gateway with a public port would change it; the page says a self-hosted Gateway is what needs a public IP. |
|---|
| Parsed numbers | |
|---|
Evidence 1
| date | source | what it proved |
|---|
| 2026-10-23 | lantunnel.app/ | 'Normal Client access does not require router port forwarding on your LAN or a public URL for each service. If you host a Gateway yourself, that Gateway needs a reachable public IP' |
More fields 5
| wg path | none |
|---|
| ingress | none |
|---|
| volume stated | No allowance is published; Relay capacity is described as a shared resource rather than a quota. |
|---|
| bytes transit | overlay-only |
|---|
| transit note | Direct QUIC when NAT allows, else encrypted relay. |
|---|
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