The authenticated control plane for exposing local services over HTTPS. Managed namespaces, child hosts, live SQLite-backed telemetry, persistent tunnels, and loopback hostnames like `l.bore.dk`, `local.bore.dk`, and `localhost.bore.dk` for localhost, APIs, React, Node.js, Next.js, Vite, webhooks, and OAuth-heavy development.
curl -sL https://bore.dk/install.sh | bashPopular guides: HTTPS local website, local API HTTPS, webhook testing on localhost, OAuth callbacks on HTTPS, HTTPS child subdomains, localhost-like loopback hostnames.
Namespaces
Managed
Telemetry
SQLite-backed
Tunnel mode
Persistent
$ bore up 3000
Authenticating with Bore control plane...
Namespace attached: pia
Public URL: https://pia.bore.dk
Status: persistent
Control Plane
Authenticated Bore session issued.
SQLite-backed account state is active.
Telemetry
Request stream connected.
Namespace and host metrics update live.
Product Intelligence
Bore combines authenticated access, namespace management, and telemetry in one control plane instead of scattering state across tunnel commands and ad-hoc scripts.
Live Console
A dashboard view for namespace health, child hosts, request stats, and tunnel activity without bouncing between tools.
Dashboard Preview
Namespace inventory
pia
pia.bore.dk
Claims
3
Hosts
5
RPM
1.2k
SQLite Auth
User records, session issuance, and namespace limits live close to the control plane for predictable access checks.
Persistence
Persistent connections keep routing stable even when teams pause and resume local work throughout the day.
Managed Namespaces
Reserve `pia.bore.dk`, attach HTTPS child hosts like `api.pia.bore.dk`, and keep tunnel ownership explicit across the team.
Namespace Rules
First-level child hosts like `api.pia.bore.dk` are persisted. Deeper trees are intentionally rejected to keep routing predictable.
Bore ships the web control plane, the local agent, and deployment primitives in the open. Audit the stack, file issues, or fork the product without reverse-engineering a black box.
Built by
Founder-facing trust signal for a developer tool is simple: public code, a real person, and a direct path to the builder.
Meet the founder