portline
http://portline.localhosthttps://crimson-otter.portline.liveLiveGive localhost
a name
Get named local URLs and instant public links for your dev servers — zero config. Inspect, replay, and debug every request with a beautiful native UI.
Portline
Running2 routes · proxy :80
landings
http://landings.localhostOne window for everything you run locally.
Name it, share it, and watch every request flow through — without touching your code.
See every request in real time
Inspect headers, bodies, and status codes as they flow through — no Chrome DevTools needed.
web.localhostNamed local URLs
Works with any framework and language.
crimson-otter.portline.live
Instant public links
Share over HTTPS in one click — demos, webhooks, devices.
Portline sits in the middle.
It names your server, optionally shares it, and records every request on the way through — so you can replay or edit & resend any of them.
browser
localhost:3000
One command. That's it.
Just prefix your command with portline and a name. Named local URLs, auto-detected ports, optional HTTPS sharing — no config, no project changes.
~/code/myapp
$ next dev
▲ Next.js · ready in 1.2s
http://localhost:3000
No inspector. No sharing. Just a port number.
~/code/myapp
$ portline myapp next dev
portline registered myapp.localhost
▲ Next.js · ready in 1.2s
Named URL. Inspector. One-click sharing.
Next.js
$ portline myapp next dev
Vite
$ portline myapp vite
Rails
$ portline myapp rails server
Go
$ portline myapp go run .
Built for every part of your workflow.
Whether you're debugging an API, sharing a demo, or testing webhooks — Portline fits in without getting in the way.
Debug APIs without leaving the terminal
Watch requests hit your local server in real time. Inspect headers, payloads, and status codes — no Chrome DevTools, no proxy config.
Share your work in progress
Send a secure HTTPS link to your local server. Teammates, clients, and reviewers can see your app running on your machine — no deploy needed.
Receive webhooks locally
Point Stripe, GitHub, or any webhook at your Portline URL. Requests arrive at your local server — inspect and replay them anytime.
Test on real devices
Open your Portline URL on a phone, tablet, or another machine on the same network. Instantly see how your app behaves across devices.
Juggle multiple services
Run API, web, and auth servers side by side — each gets its own named URL. No more juggling port numbers.
Replay and edit requests
Tap any captured request, tweak the headers or body, and resend it — perfect for reproducing flaky bugs or iterating on API design.
Simple, honest pricing.
One plan, everything included. No hidden fees.
Pro
Share your work with the world.
$8/ month
- Unlimited named .localhost routes
- Unlimited public HTTPS URLs
- Multiple simultaneous tunnels
- Extended inspector history
- Priority relay routing
Pro Annual
Save $47 vs monthlySame Pro, billed yearly.
$49/ year
- Unlimited named .localhost routes
- Unlimited public HTTPS URLs
- Multiple simultaneous tunnels
- Extended inspector history
- Priority relay routing
Team
For teams shipping together.
$18/ month
- 3seats$6/seat/mo
- Unlimited named .localhost routes
- Unlimited public HTTPS URLs
- Multiple simultaneous tunnels
- Extended inspector history
- Priority relay routing
Questions, answered.
No. You prefix your dev command: portline web next dev. Portline wraps the process and detects the port — nothing is committed, and it works with any framework.
Anything that listens on a port: Next, Vite, Rails, Django, Go, a raw HTTP server. Portline observes the process from the outside, so it never has to integrate with your build.
Your local server is exposed over an encrypted tunnel to Portline's relay and served at an HTTPS subdomain. You decide when it's on — turn it off and the URL stops resolving.
Local .localhost traffic never leaves your machine. Public tunnels are encrypted in transit, and only requests to your live URL ever reach your server.
macOS today (Apple Silicon & Intel). Linux and Windows are on the roadmap.
ngrok only gives you a public tunnel. Portline also gives you named local URLs, a built-in request inspector, and replay/edit — all from a menubar app. And local .localhost traffic never leaves your machine.
The app updates itself in the background, so security fixes reach you quickly — no manual reinstall, no stale versions.
Yes. Each service gets its own .localhost name and optional public URL. Run as many as you need — they're all visible in the menubar.
Give your localhost a name.
Install in seconds.