Home / Egress and tunnels
portmap.io
portmap.io/UDP port forward (OpenVPN based, hosted)egress/portmap-ioJSONcomparereport an errorprovider JSON
- Free allowance
- Free: One configuration setting, One forwarding rule, Random external port, Auto-generated domain name
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- per-ip-shapingunlimited bandwidth stated, no rate published
- 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 | Free: One configuration setting, One forwarding rule, Random external port, Auto-generated domain name unit unlimited; metered on none |
|---|
| Price | USD 0 |
|---|
| Limits | - per-ip-shaping (binding) unlimited bandwidth stated, no rate published source
|
|---|
| Binding | per-ip-shaping The byte allowance is unlimited by statement, so the first real failure is that the free plan's external port is random and custom external ports are a Premium feature. That is a paywall on the one property a WireGuard endpoint needs, and it is not one of the seven vocabulary kinds. |
|---|
| Identity | email an account that generates an OpenVPN configuration or SSH key: 'Create a configuration file for OpenVPN or SSH key using the Generate button' |
|---|
| Egress | 'Unlimited bandwidth' is a core feature line on the product page; no rate or tolerance is published; ingress: tcp+udp free allowance: none published |
|---|
| Interface | cli OpenVPN config or SSH key plus a mapping rule created in the dashboard or by the API |
|---|
| Tooling | OpenVPN or SSH plus the portmap.io REST API and client |
|---|
| Composes with | one rule is one port, so it composes with exactly one WireGuard interface |
|---|
| Reliability | the free rule's external port is allocated by the operator and can in principle be reassigned; the tunnel is an OpenVPN session that must stay up |
|---|
| Notes | The free tier is generous on bytes and stingy on the one thing that matters here. Re-read 2026-10-23: the 1024-65535 port range rule applies to Premium custom ports, and the free rule stays a random port. |
|---|
| Evidence note | documented Whether the random port survives a reconnect is not stated anywhere on the site, which is the open question that decides the verdict. Raise by creating a free rule, noting the port, restarting the VPN, and reading the port again. |
|---|
| Parsed numbers | - has-free-tier 1
- price USD 0
|
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-23 | portmap.io/ | free plan is one rule with a random external port; Premium USD 3.99/month adds custom external ports; 'Unlimited bandwidth'; TCP or UDP forwarding over OpenVPN |
| 2026-10-23 | portmap.io/support | 'What ports can I forward on Premium plan? The port number must be in range [1024-65535] and not occupied by another user', and 'Basic plan which allows only one mapping rule is unlimited' |
More fields 6
| wg path | inside-udp |
|---|
| wg detail | the rule forwards UDP: 'You can forward HTTP traffic to your local web-server as well as any TCP or UDP traffic.' The public port is random on the free plan and chosen on Premium. |
|---|
| ingress | tcp+udp |
|---|
| volume stated | 'Unlimited bandwidth' is a core feature line on the product page; no rate or tolerance is published |
|---|
| bytes transit | yes |
|---|
| transit note | the portmap.io server terminates the VPN and forwards the rule's 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