Plus
$2/mo
- 1 dedicated IP address
- 10 devices
- 5 open ports
- 100 GBbandwidth
- 20 Mbpsspeed
Portmap.io publishes a service through its shared server on ports it maps for you. GetAStatic gives your device its own static public IPv4 over WireGuard instead, so clients reach a fixed IP:port that you control. From $2/mo.
Not affiliated with Portmap.io. Prices as listed on their site, checked 2026-10-06.
Updated
Portmap.io's paid plan against ours.
| Feature | Portmap.io | GetAStatic |
|---|---|---|
| Price | Premium $3.99/mo | From $2/mo |
| Tunnel | OpenVPN or SSH, or its command-line client | WireGuard, with an AmneziaWG switch |
| Your own public IPv4 | No, a Portmap server address other users share | Yes, one dedicated IPv4 per config |
| External port numbers | 1024 to 65535, if no other user holds the number | Any port from 1 to 65535 that you open |
| Ports 80 and 443 | Shared, for HTTP and HTTPS rules only | Yours, for any TCP or UDP service |
| Port inside vs outside | A mapping rule per port, remote to local | The same number on the IP and the device |
| Refunds | None, per its terms | 7-day money-back guarantee |
Portmap.io facts from its home page, FAQ and terms, checked 2026-10-06. Its free plan allows one rule on a random external port.
On Portmap.io you connect your PC to a Portmap server with OpenVPN or an SSH tunnel, then add a mapping rule. A rule names a remote port on Portmap's side, the port on your PC, and optionally a host header and an allowed IP. Visitors connect to yourname.portmap.io on the remote port, and Portmap passes the traffic down the tunnel to your machine.
That design is fine for publishing one service. The limits come from the address, which belongs to Portmap's server and is shared. The free plan gets one rule on a random external port. Premium, at $3.99/mo, lets you pick ports from 1024 to 65535, but only numbers no other user holds. Ports 80 and 443 TCP are shared between users and work only for HTTP and HTTPS rules.
So SSH on 22 or RTSP video on 554 cannot keep its usual port. A partner who wants one IP to allowlist gets a server address that other customers use too. And every client has to know the remote port the rule assigned, which often differs from the port the service listens on.
Plus for light use, Pro for most people, Ultra for full gigabit.
5× speed · 10× bandwidth · 2 IPs — only $2/mo more
Neither design is better for every job. If you only want to publish a service through a tunnel and do not mind which address or port it lands on, a Portmap mapping does that.
GetAStatic works at the address level instead. A dedicated public IPv4 is assigned to your WireGuard tunnel. Every port starts closed. When you open one in the dashboard, TCP or UDP, connections to that IP and port reach your device on the same number. There is no remote-to-local mapping, and the device's outbound traffic leaves from the same IP, so it works as a VPN too. This makes more sense when you want a stable IP:port endpoint that you control.
Some things move to your side. Portmap routes by host header on its shared 80 and 443, and Premium adds SSL certificates. With your own IP you run that yourself, for example a reverse proxy with a Let's Encrypt certificate. A custom domain becomes an A record that points at the IP, not a CNAME to a portmap.io name.
Keep the Portmap mapping running until the new address passes a test from outside.
| Port | Protocol | Used for |
|---|---|---|
| 22 | TCP | SSH, on its usual port |
| 3389 | TCP+UDP | Windows Remote Desktop |
| 5900 | TCP | VNC remote support |
| 554 | TCP | RTSP video from an IP camera or NVR |
Portmap.io
client -> yourname.portmap.io:34567 (shared Portmap server)
-> mapping rule 34567 -> 3389
-> OpenVPN or SSH tunnel
-> your PC :3389
GetAStatic
client -> YOUR-IP:3389 (your dedicated IPv4)
-> port 3389 open in the dashboard
-> WireGuard tunnel
-> your PC :3389Plus allows 5 open ports; Pro and Ultra have unlimited open ports. A range counts as its size.
Yes, but the device must listen on that number, because traffic arrives on the same port it was sent to. If a rule mapped 34567 to 3389, either open 3389 and give clients the new port, or open 34567 and set the service to listen on 34567.
Only while the Portmap rule exists, because that name points at Portmap's server. Use your own domain with an A record for the new IP, or share the IP itself. Remove the old rule once clients have moved.
No. The WireGuard app, or WireGuard on your router, replaces it. After the new address passes an outside test, stop OpenVPN and remove it from startup so the PC does not keep two tunnels.
Yes. Open 443 TCP, point each domain's A record at your IP, and run a reverse proxy such as Caddy or nginx that routes by hostname. Port 443 on the IP is yours, so no other customer competes for it.
Have more questions? See the full FAQ →