Localify gives every local project a clean .localify address with trusted HTTPS, so developers can use stable local domains instead of juggling localhost ports.

Does Localify put my work online?

No. Localify is a local development proxy, not a public tunnel. Your local services stay on your machine.

Do I need to edit /etc/hosts or install mkcert?

No. Localify handles the local resolver, local certificate authority, and Node trust setup during onboarding.

Get Localify

The modern
local domain toolkit

A native macOS toolkit for stable .localify URLs, local DNS, and browser-trusted HTTPS.

Try for free Buy license

Available on macOS. Linux & Windows coming soon.

Projects

⌘F

Acme

acme.localify

Hooli

hooli.localify

pied-piper

pied-piper.localifymiddle-out.localify

From a folder to a live URL,
in five moves.

Install once, bring your projects in, and switch between them by hostname instead of by port. No mkcert, no /etc/hosts, no ngrok — just your apps, with clean URLs.

One permission prompt. We handle the rest.

Localify installs the local CA, registers the CLI, routes .localify DNS, and configures Node trust. No mkcert dance, no /etc/hosts edits, no env exports to remember.

Drop a folder. We fill in the rest.

Point Localify at a project folder — it scans it, detects each app, and proposes hostnames. You review and confirm. Seconds, not config files.

localify init, straight from your editor.

If your hands are already on the keyboard, run localify init from your editor terminal. Interactive prompts, same result — the project shows up in the app.

Projects by name, not by port.

Every project gets its .localify hostnames with trusted HTTPS. Four tabs that each say something, demos that look like a product, and envs that stop breaking when a port shifts.

One-click editor and dev server.

Each project card opens its folder in your editor and starts the dev server if it's down. The main view doubles as a dashboard — one place to see which of your projects are actually up.