Loopback Hostnames for Local Development on Bore

Step 1

Keep your local app on its normal port

Run the local website or API on the same port you already use, such as 3000, 5173, 8080, or 8787.

Step 2

Open the Bore loopback hostname on that port

Use any of the Bore loopback hostnames directly in the browser, including `l.bore.dk`, `local.bore.dk`, or `localhost.bore.dk`.

http://l.bore.dk:3000
http://local.bore.dk:5173
http://localhost.bore.dk:8080

Step 3

Use child hosts when one hostname is not enough

Host-based routing and multi-origin local setups can use child hosts under the same loopback namespace.

http://api.l.bore.dk:3001
http://auth.local.bore.dk:3000
http://admin.localhost.bore.dk:4173

Step 4

Use Bore tunnels only when you need outside access

The loopback hostnames are for local-only access on your own machine. Switch to `bore up` when a phone, teammate, webhook sender, or OAuth provider needs to reach the service from outside your computer.

What do l.bore.dk, local.bore.dk, and localhost.bore.dk do?

They give you Bore-managed hostnames that resolve to 127.0.0.1 for local development. That means your browser can use a named host instead of plain localhost or a raw loopback IP.

Can I use subdomains like api.l.bore.dk or app.local.bore.dk?

Yes. Bore supports child hosts under these loopback names, so you can test host-based routing and split local origins on your own machine.

Are these hostnames public?

No. They are meant to point back to your own local machine at 127.0.0.1, so they are useful for local-only browser and development workflows rather than public sharing.