vercel-labs/portless

Replace port numbers with stable, named local URLs. For humans and agents.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 1st, 2026
Created on February 15th, 2026
Open Issues & Pull Requests: 129 (+0)
GitHub issues: Enabled
Number of forks: 406
Total Stargazers: 12,276 (+3)
Total Subscribers: 25 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 14.8 days
90th percentile: 47.3 days
Tracked items: 119

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 50% of tracked open issues have had no activity in three months. Only 10% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 72
New in 7 days: 5
Closed in 7 days: 0
Avg open age: 100 days
Stale 30+ days: 47
Stale 90+ days: 31

Recent activity

Opened in 7 days: 5
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 9

Top labels

  • enhancement (7)
  • bug (5)
  • question (1)

Detailed Description

Portless is a development tool that replaces port numbers with stable, named local URLs for local services.

The problem it solves is the friction of managing multiple localhost ports during development. When running several services locally, developers must remember which port corresponds to which service, and these ports can conflict or change between environments. Portless intercepts local network traffic and maps services to human-readable domain names like localhost.myservice, eliminating the need to track port numbers. This approach works by providing stable URL routing that persists across sessions, making it easier for both developers and automated agents to reference and access local services.

The tool suits developers working with microservices architectures or multiple concurrent services during local development. It is particularly valuable when you need consistent, memorable URLs for services rather than managing a mental map of port assignments. The stable naming scheme also benefits automation and testing scenarios where services need to be reliably addressable by name rather than port number.

The project shows active development with regular commits and ongoing refinement of its core functionality. The codebase demonstrates attention to both the developer experience and technical implementation details. The project maintains a clear focus on its specific problem domain without scope creep into adjacent concerns.