LocalCan alternative
LocalCan and lokei both connect local HTTPS, public URLs, and traffic inspection. LocalCan is a visual proxy and tunnel manager built around services you point it at; lokei is a CLI workflow built around the project you are standing in.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupThe biggest distinction is whether the product manages endpoints or the project lifecycle behind them.
Scroll horizontally to see every column.
| Capability | lokei | LocalCan | Official evidence |
|---|---|---|---|
| Primary interface | CLI commands designed to run inside an existing project folder | Desktop application plus a CLI and YAML project files | |
| Local domain model | Machine-local .test names resolved through a local DNS service | .local names published with mDNS for the machine and local network | |
| Application startup | Detects and starts the framework, package script, Compose stack, Sail project, or declared services | Routes to a configured target such as localhost:3000; the application remains an external upstream | |
| Public URL model | Project-aware share sessions with stable project names, requested subdomains, password or token protection, TTLs, and custom domains by plan | Service endpoints whose LocalCan URL can remain reserved for up to seven days, plus offline snapshots and verified custom domains | |
| Traffic inspection | Browser-based local inspector with filtering, editable replay, retention, and HAR export | Desktop inspector for local and public traffic with bodies, keyboard navigation, and replay | |
| Protocols | Local and public HTTP application workflows | HTTP, HTTPS, and raw TCP tunnels |
LocalCan has broader endpoint and desktop controls. lokei has deeper project startup and service context.
Scroll horizontally to see every column.
| Capability | lokei | LocalCan | Official evidence |
|---|---|---|---|
| Trusted HTTPS | One-time setup trusts a local CA and automatically issues route certificates | A local CA secures .local domains after it is trusted through the app or setup flow | |
| Phone and LAN access | Local .test routing is designed for the configured development machine | mDNS publishes .local domains to devices on the same Wi-Fi network | |
| Multiple local services | Creates project and service subdomains from discovered or declared public HTTP services | A YAML project groups one or many services, each with local and public endpoints |
Scroll horizontally to see every column.
| Capability | lokei | LocalCan | Official evidence |
|---|---|---|---|
| Zero-argument run command | lokei run detects the current project and launches its normal development command | localcan http or https takes a port; saved projects take explicit target URLs | |
| Framework configuration | Injects framework-specific host, port, and application URL settings for supported stacks | Framework-agnostic proxy; headers and target URLs can be configured per endpoint | |
| Docker and dependent services | Discovers Compose and Sail, starts them, and distinguishes public HTTP services from private infrastructure | Can proxy any reachable container target and group several services, without owning their container lifecycle |
Scroll horizontally to see every column.
| Capability | lokei | LocalCan | Official evidence |
|---|---|---|---|
| Share from project context | Resolves the active route, starts the project if necessary, and creates one service-aware share session | Attaches a Public URL to a configured service or creates a quick tunnel for an explicit port | |
| Stable and custom public names | Supports project-based and requested public names plus verified custom domains through lokei cloud plans | Reserves a paused LocalCan URL for up to seven days and can map verified custom domains to services | |
| Inspector availability | The inspector is served as a local web application and works with lokei-routed traffic | The full viewer is desktop-only; the Linux CLI records data but does not include the viewer |
Both cover local and public traffic; the advantages are on opposite sides of the upstream boundary.
Endpoint management with a strong visual and cross-device workflow.
Application and service lifecycle attached to the route.
Choose based on whether visual endpoint control or automatic project execution removes more work.
Keep the LocalCan YAML and license configuration while testing lokei. The only immediate conflict is ownership of the standard proxy ports.
LocalCan and lokei can both remain installed, but their default local HTTPS listeners cannot own port 443 at the same time.
Answers about local networks, project startup, public URL persistence, and inspection.
Yes. It overlaps across local HTTPS domains, public URLs, custom domains, project configuration, and traffic replay. LocalCan is endpoint- and desktop-oriented; lokei is project- and CLI-oriented.
LocalCan has the clearer local-network workflow because it publishes .local domains through mDNS to devices on the same Wi-Fi. lokei can create a public share URL for device testing, but it does not document an equivalent dedicated LAN discovery mode.
Its documented model points domains and tunnels at a target such as localhost:3000. lokei detects and launches the project command, Compose stack, Sail project, or declared services before routing them.
Yes, subject to their hosted plans and domain verification. LocalCan documents verified custom domains as persistent service endpoints; lokei supports custom-domain controls through its cloud sharing capabilities.
Both provide body inspection and replay. LocalCan offers a polished desktop inspector for local and public traffic. lokei serves a browser-based inspector and adds filtering, editable replay, retention controls, and HAR export within its project workflow.
No. lokei focuses on HTTP applications. LocalCan supports raw TCP tunnels, so it is the stronger choice when a database, SSH service, or another non-HTTP endpoint must be exposed.
Yes, but not with both default HTTPS proxies active because each expects port 443. Pause or reconfigure one local proxy before starting the other.
LocalCan claims use its public product, CLI, project, Public URL, and inspector documentation. lokei claims use its public website and npm package documentation.
Verified July 16, 2026. Product behavior and commercial availability can change. LocalCan is a trademark of its respective owner. lokei is not affiliated with or endorsed by LocalCan. This page distinguishes the documented desktop viewer from the Linux CLI rather than assuming platform parity.
$ lokei run
Install lokei, complete setup once, then run it inside an existing application without creating a port mapping first.
npm install -g @ulpi/lokei && lokei setup