Home / Egress and tunnels
Wiredoor
www.wiredoor.net/Self hosted WireGuard ingressegress/wiredoorJSONcomparereport an errorprovider JSON
- Free allowance
- 'Expose HTTP, TCP, and UDP services from private networks through outbound WireGuard tunnels.
- Verdict
- self-hosted, last resortverdict paid-only: no free allowance; listed for its price. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- no price statedsee Price below
- Identity
- anonymousno card, no phone
- Binding limit
- volume-quotathe software imposes no byte meter; what runs out is the monthly allowance of the host it runs on, and that host is a separate provider
- 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 | 'Expose HTTP, TCP, and UDP services from private networks through outbound WireGuard tunnels. Keep control of your public endpoint, routing, certificates, and access policies.' The software is self-hosted; no vendor plan and no vendor quota. unit unlimited; metered on none |
|---|
| Price | USD 0 |
|---|
| Limits | - volume-quota (binding) the software imposes no byte meter; what runs out is the monthly allowance of the host it runs on, and that host is a separate provider source
|
|---|
| Identity | anonymous Self-hosted: the only account is the local admin the installer creates ('username: admin@example.com'). No vendor registration. |
|---|
| Egress | No allowance is published because there is no vendor in the path: the server's NIC and its hosting bill are the limit.; ingress: tcp+udp free allowance: none published |
|---|
| Interface | cli 'wiredoor http first-app --domain app.example.com --port 3000' |
|---|
| Tooling | wiredoor CLI, Docker, the server dashboard |
|---|
| Composes with | runs on the same free-tier VPS as Pangolin or Wireport, so the three are alternatives rather than additions; the VPS egress is the shared ceiling |
|---|
| Reliability | the public endpoint is the operator's; its uptime, certificate renewal and firewall are all local work |
|---|
| Notes | The second half of the ingress chain is missing: Wiredoor Server must sit on a host with a public IP. It is software, not a service, so the free tier is the VPS, not Wiredoor. The FAQ page was read through the search index rather than a direct fetch, which is why its evidence row is weaker than the home page. |
|---|
| Evidence note | documented A live UDP listener on a Wiredoor server would raise this to measured. No server was stood up. |
|---|
| Parsed numbers | - has-free-tier 0
- price USD 0
|
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-23 | www.wiredoor.net/ | 'Expose HTTP, TCP, and UDP services from private networks through outbound WireGuard tunnels'; 'Route web applications by domain or path and TCP or UDP services by an approved public port' |
| 2026-10-23 | www.wiredoor.net/documentation/faq | 'Wiredoor assign unused port automatically in the range defined by TCP_SERVICES_PORT_RANGE', via the search index snippet |
More fields 6
| wg path | none |
|---|
| wg detail | 'Remote nodes connect outward to Wiredoor Server, and forwarded traffic crosses the encrypted tunnel.' The wiredoor CLI or the dashboard token holds the tunnel; no .conf export is documented. |
|---|
| ingress | tcp+udp |
|---|
| volume stated | No allowance is published because there is no vendor in the path: the server's NIC and its hosting bill are the limit. |
|---|
| bytes transit | yes |
|---|
| transit note | the server receives on its public port and forwards down the outbound WireGuard tunnel to the private node |
|---|
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