Skip to content
All posts
5 min read

Introducing Localport: tunneling you can inspect

We built Localport because localhost tunneling should be flexible, transparent, and work behind any network. Here is what ships in v1 and why it matters.

announcement

Today we're releasing Localport, a tunneling platform that gives your local services a public URL with a transparent agent you can read on GitHub.

Why we built this#

We've used tunneling tools for years. We kept meeting the same limits. Protocols were split across plans. Pricing was per seat. The program between our machines and the internet was closed. And we could not find one tool for the two things we needed most, private access to devices in the field and one webhook URL for a whole team.

We wanted something that:

  • Supports HTTP, TCP and TLS tunnels on every plan
  • Charges one flat price per team
  • Delivers one webhook to every teammate
  • Gives private access to devices in the field, with a record of every connection
  • Ships an agent you can read on GitHub before you run it

So we built it.

What Localport does#

For web developers. One command to share your local app. You get an HTTPS URL with a real certificate every browser trusts. Works with React, Next.js, Django, Rails, Flask, anything.

localport http 3000 --token YOUR_TOKEN
# → https://my-application.eu.localport.dev

For backend developers. TCP tunnels for databases, SSH, and custom protocols. Your Postgres on localhost:5432 gets a public address on every plan.

localport tcp 5432 --token YOUR_TOKEN
# → my-application.eu.localport.dev:47266

For teams. Fanout delivers each webhook to every connected teammate. When Stripe sends an event, everyone on the team receives it on their own machine.

For devices in the field. Remote Access reaches any port you open on a device, from anywhere, behind NAT and CGNAT. Devices are private by default, and you choose which people and machines reach each one.

The agent is on GitHub#

The Localport agent is a single Go binary with zero runtime dependencies. Its source lives on GitHub. You can read every line, build it from scratch, and audit the tunnel protocol.

We believe the tool that sits between your machine and the internet should be transparent. You should be able to see exactly what it does with your traffic before you ever run it.

What you get#

Every plan includes:

  • HTTP, TCP and TLS tunnels
  • HTTPS with publicly trusted certificates
  • A URL that stays the same across restarts, and custom domains
  • Fanout for team webhooks
  • IP allowlists, basic auth, header authentication and webhook signature verification

Remote Access is part of the Pro, Business and Enterprise plans. Each plan is one flat price for the team. See pricing.

What's next#

If you have ideas or run into a problem, open an issue on GitHub or email support@localport.io.

Get started →

Back to all posts