Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Port Zero

How I learned to stop worrying and love PORT=0

Details

External ID
49063648
Source
HN
Company
—
Product
Port Zero
Website domain
portzero.net
Launched
July 27, 2026
Cohort
—
Upvotes
19
Upvotes percentile
0.7037037037037037
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Hi HN,Recently I wasted several hours wrangling my dev environment only to find out that the browser frontend was talking to the wrong version of the backend. This got me thinking--why on earth are we still using simple numbers to describe which process to connect to? Why not use names instead? I thought of all the times a program wouldn't start because of port conflicts. The more I thought about it, the crazier it seemed.Modern operating systems already offer no-conflict ports: if you make your TCP server listen on port 0, the OS assigns you a random available port. But that only solves half the problem.I built the other half: PortZero. It's a GPLv3 program that watches for processes (and docker containers!) with a special PZ_TUNNEL environment variable: PZ_TUNNEL=myapp-{branch}.portzero.local:80 npm run dev When it sees such a process or container, PortZero does this:1. Create a virtual NIC (if it hasn't already)2. Create a new virtual IP address3. Create a DNS record that substitutes things like {branch} based on the working directory of the process, and points at that virtual IP address4. Start listening on that virtual IP address on the port of your choice (e.g. port 80 for http, port 443 for https, port 5432 for postgresql)5. Forward any TCP connections to that virtual IP address / virtual port to the random, OS-assigned port that your process or container is actually listening onThe result is you don't have to think about ports anymore, you just have to think about subdomains. You can have multiple services available on port 80 without conflicts, as long as they have different portzero.local subdomains.It does some other cool stuff like:- Enable HTTPS on local HTTP services by creating a local CA and registering it on your machine- Enable cloud tunnels so you can access your apps on other devices (paid feature)Links:https://portzero.net/docs/https://github.com/PortZeroNetwork/portzero

Enrichment

Theme
proxy, dns, and networking tools
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
guide to using port 0 in development
Manually corrected
False

Could you build this?

Partial The marketing and configuration UI is straightforward, but running a local daemon that dynamically intercepts random OS ports, manages local DNS (.localhost), and operates a local reverse proxy requires systems-level networking code.

What it would actually take: A real implementation requires a lightweight background daemon (written in Go or Rust) managing an embedded reverse proxy and local DNS server or hosts-file resolver. The challenging parts are multi-platform support (handling macOS/Linux/Windows DNS resolution seamlessly via system daemons or loopback aliases) and intercepting port 0 allocations to bind named virtual hosts automatically without administrative conflicts. Requires solid systems networking and OS IPC knowledge.

Discussion

20 comments analyzed.

Competitors mentioned: Cloudflare Tunnels (free alternative for cloud access), Tailscale (lower-cost VPN/tunneling solution), SRV records (DNS-based service discovery), VS Code debugger (for port conflict detection)

Concerns raised: Pricing too high ($50/month) relative to effort and operating costs, Minimal differentiation from free alternatives like Cloudflare Tunnels, Unclear what priority support actually includes, Origin story unconvincing (simple port numbering is straightforward enough), Limited genuine use case when developers already have working solutions

Feature requests: Support for IPv6 localhost addressing, SRV record integration (though noted as requiring broad ecosystem support), Automatic HTTPS configuration

Competitors

Other products that read as similar to this one — 95 launches clear the similarity bar, closest 8 shown.

Attention rank: #39 of 96 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 265 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.