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 address

3. Create a DNS record that substitutes things like {branch} based on the working directory of the process, and points at that virtual IP address

4. 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 on

The 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

I Championed Prediction Markets. Look What They've Become

Triton: DirectX 11 Driver for QEMU

Show HN: Simple HIIT timer for efficient workouts

How the Atmos Clock Functions

PGSimCity - How PostgreSQL Works

Show HN: Turn an image into a 3D blockbench model

DLC Protect – Open-Source ECDH Encryption for Steam DLCs

Liveness proofs in Veil: Part 1

Open coordination stack for lattice-building robot swarms

Quebec scraps AI and automation projects in the public sector

Odella [video]

Show HN: Blind-box commerce made easy

Unlocking the Halo: Campaign Evolved Secret Debug Menu

UBI-ticon: High Effort Feature Film using programmatic sonification

Open-source 3D-printed portable MRI machine built for under $70k

Show HN: Port Zero – how I learned to stop worrying and love PORT=0

Data centres in NZ: Jobs creators or destroyers?

Qwen 27B with local well writen tools just as powerful as cluade models?

From A.I. To the Deep State, Michel Foucault Foresaw It All

A Personal Note from Our Founder (2025)

Visualizing the Artemis II Mission

Ask HN: Is Zig worth it over Rust in 2026?

Most Googlebots Are Fake

Jeffy Loop, an autonomous code improvement loop for Claude Code

Fonts In Use – Find out where a font is used

From Soft to Hard Skills

Show HN: Lowkey Studio – Shader Powered visual effects compositor in the Browser

AI Moves into Family Life

How to self-host servers in your living room on static IPs

Show HN: Distill and serve small models with frontier quality for half the cost

Show HN: Raw Binary Program Analysis Tool