Introducing Localhhost 0.1.1Explore

Your local work deserves
a place on the web.

Give your dev server a real address. Localhhost brings local HTTPS, shareable public URLs, and a clear view of every request into one desktop app. Keep building. Let the right people in.

Localhhost showing local HTTPS domains, certificate status and the ports they connect to.

At home with the tools you already build with.

ViteNext.jsDjangoAstroRails

Every request tells a story. See the whole thing.

A webhook that fired once at three in the morning is still there, with the body it sent and the status you returned. Pick a row to read it, press Enter to send it again, and stop reconstructing the story from a log line.

Headers and bodies, request and response

Explore the inspector
The Requests screen: captured exchanges with method, host, path, status and duration.

Your whole project. In one place.

Group the domains and URLs of one project and everything narrows to it — what it holds, what is live, what it has served. The project lends its rules to all of it, so a password is set once instead of on every endpoint.

A repository can describe its own, in a localhhost.yml it carries

Bring your projects
A project page listing its addresses, what is live, and the traffic it recently served.

The Localhhost stack

Three layers over the port you are already listening on. Take one, take all three.

01

Local domains

localhhost domain add shop 3000

shop.local answers over HTTPS, from this laptop and from the phone next to it. A certificate authority made on your machine signs it, so the padlock is green and nobody else ever issued anything.

02

Public URLs

localhhost tunnel 3000

An https address anyone on the internet can open, pointed at a port on this machine. Instant ones are free and change on every start; sign in and the name stays put across restarts.

03

The inspector

localhhost traffic --follow

Every exchange that went through either, with its headers and its bodies, the endpoint that served it and which side of the wire it came from. Replay one, or freeze a few into a page you can send.

What sharing a port leaves out

A tunnel is the part everyone knows about. It is also the part that leaves the most out.

A name on your own network

shop.local resolves on the Wi-Fi with the internet unplugged. Your phone opens it over HTTPS with nothing installed on it.

A record you keep

Exchanges live in memory on this machine. There is no dashboard to log into, no retention window, and nothing to lose when a plan ends.

Rules in front of the server

A password, a list of allowed IPs, a secret link — applied by the proxy before a request ever reaches your code.

One place for many

A project holds its domains and its URLs together, lends them all the same rules, and starts or stops them in one go.

Fits what you already run

Your dev server

Vite, Next, Django, Rails, anything on a port. Localhhost never asks what it is.

Your phone

The same address opens on any device on the Wi-Fi, over HTTPS, with no configuration on it.

Your webhooks

Stripe, GitHub and the rest reach a public URL, and every delivery is recorded and replayable.

Your terminal

A CLI does everything the window does, and an MCP server lets a coding agent drive it.

It runs on your machine, and stays there

The proxy, the certificate authority and the recorded traffic are all local. Nothing is uploaded unless you press share, and a public URL exists only while you keep it running.

Your own CA

Made on this machine, installed once, never leaves it.

Local recording

Exchanges live in memory here, not in anyone's cloud.

Access rules

Password, allowed IPs and a secret link, enforced in front of your server.

Open to read

One desktop app. No telemetry. Your development traffic stays under your control.

Get Localhhost

Version 0.1.1. Free, and it updates itself.

macOS is not built yet. Leave an address and you will get one email when it is.