Lokei
A cross-platform development tool that gives every local project a stable, trusted HTTPS domain without manual port, proxy or certificate setup.
The problem worth solving
Localhost stops being simple as soon as an application has several services, webhooks, secure cookies, mobile clients or multiple worktrees. Ports drift, certificates expire and every developer rebuilds the same fragile routing setup.
What I built
Lokei detects more than thirty common frameworks and development stacks, assigns stable ports and routes services through locally trusted HTTPS domains. A project can keep the same address while the underlying process, framework or worktree changes.
The same workflow extends to multi-service repositories, Docker Compose and Laravel Sail. Built-in traffic inspection and named public tunnels make it possible to debug requests or receive external callbacks without replacing the local domain model.
What the product does
- Automatic framework detection, port allocation and locally trusted TLS certificates.
- Stable project domains across macOS, Linux, Windows and Windows Subsystem for Linux.
- First-class handling for multi-service workspaces, Docker Compose and git worktrees.
- A traffic inspector and named public tunnels for debugging external callbacks.
Why the design matters
Lokei makes a named HTTPS address the default local entry point instead of something each developer configures by hand. The result behaves more like production and removes a class of setup work that otherwise returns in every repository.
My role
Ciprian created Lokei and leads the product, command-line experience, local proxy architecture and cross-platform implementation as an open-source tool.