LocalTunnel alternative
LocalTunnel is intentionally small: give it a port and it gives you a public HTTPS URL. lokei expands that moment into a project workflow by starting the application, naming it locally, inspecting it, and sharing one or several public services with their project context intact.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupLocalTunnel optimizes one port-to-URL action; lokei optimizes the development session around it.
Scroll horizontally to see every column.
| Capability | lokei | LocalTunnel | Official evidence |
|---|---|---|---|
| Starting command | lokei share or lokei run from the project directory | lt --port 8000 or npx localtunnel --port 8000 | |
| Required input | A detectable or configured project; the port is resolved automatically | The local port, with optional local host and requested subdomain | |
| Application startup | Starts frameworks, package scripts, Compose, Sail, or declared services before sharing | Connects to the local server and reconnects after that server restarts; it does not launch the app | |
| Local development URL | Trusted project.test HTTPS exists independently of public sharing | Creates a public localtunnel URL; no named private local-domain workflow is documented | |
| Public subdomain | Stable project-based names, requested vanity subdomains, and custom domains through lokei cloud plans | A unique public URL is assigned; a requested subdomain may not be available | |
| Programming interface | CLI and project configuration designed for interactive and agent workflows | CLI plus a Node API that creates and closes tunnels programmatically |
A small surface is a LocalTunnel strength. The question is whether the work around the tunnel is still manual.
Scroll horizontally to see every column.
| Capability | lokei | LocalTunnel | Official evidence |
|---|---|---|---|
| Public HTTPS | Managed HTTPS is built into public project shares | Every LocalTunnel session receives a public HTTPS URL for the selected port | |
| HTTPS to the local upstream | The local lokei route terminates trusted TLS and proxies to the detected application | Client options support a local HTTPS upstream, local certificate, key, CA, or invalid-certificate allowance | |
| Custom tunnel service | Uses lokei's hosted sharing service for managed project sessions | The client host option can point at an alternative LocalTunnel-compatible proxy service |
Scroll horizontally to see every column.
| Capability | lokei | LocalTunnel | Official evidence |
|---|---|---|---|
| Framework detection | Detects 30+ stacks, starts their normal command, and injects host, port, and URL settings | Framework-neutral tunnel; the already-running server determines behavior | |
| Docker and Laravel Sail | Discovers and starts the stack, then chooses shareable HTTP services | Can tunnel a published container port but does not manage Compose or Sail lifecycle | |
| Monorepo sharing | One project share session can contain selected public services and their dependencies | Each client tunnel targets one port; several services require several coordinated tunnel instances |
Scroll horizontally to see every column.
| Capability | lokei | LocalTunnel | Official evidence |
|---|---|---|---|
| Request visibility | Shows headers and bodies for local and shared HTTP traffic in a browser inspector | The Node tunnel object emits a request event containing method and path information | |
| Replay and export | Supports editable replay and HAR export | No replay or HAR workflow is documented in the client API | |
| Session management | Provides project share status, add, targeted stop, and all-service stop commands | The CLI session remains active until stopped; the Node object exposes close and lifecycle events |
LocalTunnel wins on minimalism; lokei wins when the tunnel cannot be separated from the project lifecycle.
A small, familiar, open-source path from one port to one public URL.
The port and tunnel become implementation details of a working project.
Choose based on how much context the sharing command needs to own.
A LocalTunnel project usually has little persistent configuration, so evaluation is straightforward.
Keep LocalTunnel in tests that specifically depend on its Node API until equivalent automation has been designed around lokei's CLI.
Answers about ports, startup, subdomains, inspection, Node automation, and multi-service projects.
Yes. If a server is already running and you know the port, npx localtunnel --port 8000 is deliberately hard to beat. lokei becomes valuable when finding the port, starting the app, local HTTPS, inspection, or several related services are also part of the job.
No. It connects to the selected local port and can reconnect if that upstream restarts. lokei detects and launches the project or stack before it creates local and public routes.
Yes. LocalTunnel assigns a public HTTPS URL to the session. lokei creates a managed HTTPS share for the active project and also provides trusted local HTTPS when the project is not public.
The client lets you request a subdomain, but its official documentation warns that the requested name may not be assigned. lokei uses project-based public naming and offers custom-domain capabilities through its hosted service.
lokei provides a full browser inspector with bodies, filters, editable replay, retention, and HAR export. LocalTunnel's Node API emits a lightweight request event with method and path, but it does not document an equivalent replay interface.
lokei can discover or declare both services, model their dependency, and share them in one session. LocalTunnel requires a separate port tunnel for each service and leaves naming and lifecycle coordination to your scripts.
Yes. Its Node API is a genuine advantage for tests and programmatic tunnel creation. lokei is designed primarily as a project CLI and agent workflow, so preserve LocalTunnel where direct library embedding is the requirement.
LocalTunnel claims use its official website and public client repository documentation. lokei claims use the public website and npm package documentation.
Verified July 16, 2026. Hosted service behavior can change independently of the open-source client. LocalTunnel is a trademark of its respective owner. lokei is not affiliated with or endorsed by LocalTunnel. Requested subdomains are described as requests, not guaranteed reservations.
$ lokei run
Install lokei, complete setup once, and share the application from its folder without looking up its port.
npm install -g @ulpi/lokei && lokei setup