Cloudflare Tunnel alternative for development
Cloudflare Tunnel is a connectivity layer between an origin and Cloudflare's global network. lokei is a local-development layer that starts with the project, gives it a private HTTPS identity, and opens a public share only when the developer asks.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupOne product begins with an origin address; the other begins with a development project.
Scroll horizontally to see every column.
| Capability | lokei | Cloudflare Tunnel | Official evidence |
|---|---|---|---|
| Starting point | The project directory, its detected command, and its local route | An already-running origin URL such as http://localhost:8080 | |
| Fast public share | lokei share resolves and starts the project, authenticates if required, and creates a project share session | cloudflared tunnel --url creates a random trycloudflare.com URL without an account | |
| Local HTTPS before sharing | Every active route receives a trusted local .test URL | The documented local preview begins with localhost and produces a public tunnel URL | |
| Stable or owned public hostname | Project names and custom-domain capabilities are managed by the lokei sharing service | Named tunnels attach a published application route to a hostname in a Cloudflare-managed zone | |
| Application lifecycle | Starts frameworks, package scripts, Compose, Sail, and declared project services | Runs cloudflared and forwards to the configured origin; the application lifecycle stays separate | |
| Platform scope | Local HTTP development, inspection, and temporary collaboration | Private-network connectivity, published applications, Cloudflare Access, and edge security services |
Cloudflare's broader edge capabilities are strengths, not missing lokei features. The comparison focuses on the local-development decision.
Scroll horizontally to see every column.
| Capability | lokei | Cloudflare Tunnel | Official evidence |
|---|---|---|---|
| Project and framework detection | Discovers the current framework and injects the host, port, and application URL settings it needs | Framework-neutral; the user supplies the local service URL to cloudflared | |
| Docker and multi-service startup | Starts Compose or Sail and identifies public HTTP services, private infrastructure, and dependencies | A named tunnel can publish several configured hostnames, but it does not start the Compose or application services | |
| Local request inspector | Captures local routed traffic with bodies, filters, editable replay, and HAR export | The quick-tunnel workflow forwards traffic through Cloudflare; an equivalent local replay inspector is not part of the documented command |
Scroll horizontally to see every column.
| Capability | lokei | Cloudflare Tunnel | Official evidence |
|---|---|---|---|
| Account requirement | Local development needs no account; hosted sharing resumes through browser authentication when the developer is signed out | Quick tunnels need no account, while named tunnels and owned hostnames use a Cloudflare account and zone | |
| Recipient requirement | A recipient opens the public URL without installing lokei or creating an account unless protection was enabled | A quick or public hostname opens in a browser; Cloudflare Access can add an identity policy when desired | |
| Quick-tunnel limits | Sharing limits and expiry belong to the selected lokei cloud plan and share session | TryCloudflare is for testing, has a 200 concurrent-request limit, and does not support Server-Sent Events |
Scroll horizontally to see every column.
| Capability | lokei | Cloudflare Tunnel | Official evidence |
|---|---|---|---|
| Edge services | Different scope: the public relay exists for temporary development sharing | Published applications can use Cloudflare CDN behavior, WAF, DDoS protection, and Access controls | |
| Non-HTTP services | Different scope: public shares expose HTTP applications | Cloudflare Tunnel supports other private-network protocols, though some require cloudflared on the client | |
| Long-running infrastructure | Designed for development sessions rather than production origin connectivity | Named tunnels can run as managed connectors with persistent DNS routes to private origins |
The decision is usually project convenience versus Cloudflare infrastructure control.
A mature bridge from private origins into the Cloudflare network.
The developer can express the intent to run or share a project instead of an origin port.
Choose Cloudflare for edge connectivity; choose lokei for the local application lifecycle.
You can keep Cloudflare Tunnel for owned domains or private infrastructure while moving local project startup and ad-hoc collaboration to lokei.
This is a division of responsibilities, not a recommendation to dismantle production or private-network Cloudflare Tunnel deployments.
Direct answers about quick tunnels, accounts, domains, SSE, and project startup.
It can replace Cloudflare Quick Tunnels for the specific job of sharing a local HTTP development project. It does not replace Cloudflare Access, private-network connectivity, WAF, owned-zone ingress, or long-running production connectors.
Cloudflare Quick Tunnels do: cloudflared tunnel --url points at an existing local origin and returns a random trycloudflare.com URL. lokei local development needs no account, but lokei share requires a free cloud account and automatically resumes after browser authorization.
No. Its documented development workflow expects an already-running service URL. lokei detects and starts the application, waits for it to become ready, and then creates the local route or public share.
Yes. A Cloudflare named tunnel publishes a hostname in a domain managed by the account. lokei supports custom public-domain capabilities through its hosted sharing service. The setup and ownership models differ, so compare the exact plan and DNS requirements before moving a registered callback URL.
No. Cloudflare documents that Quick Tunnels do not support SSE and recommends a named tunnel for streaming services. lokei is designed to proxy modern development traffic, including long-lived HTTP connections, through its local and sharing workflow.
lokei is better when the command should discover services, start dependencies, keep private processes internal, and share one or several public services coherently. Cloudflare Tunnel can publish multiple configured origins, but it does not model or start the monorepo lifecycle.
Yes. Use lokei for named local HTTPS, project startup, inspection, and temporary previews. Keep Cloudflare Tunnel wherever you need an owned Cloudflare hostname, Access policy, private network, or long-running connector.
Cloudflare claims use official Tunnel setup and local-preview documentation. lokei claims use the public website and npm package documentation.
Verified July 16, 2026. Cloudflare limits and product behavior can change. Cloudflare is a trademark of its respective owner. lokei is not affiliated with or endorsed by Cloudflare. Quick Tunnel limitations are kept separate from named-tunnel capabilities throughout this page.
$ lokei run
Install lokei, run setup once, then start and share an existing project from its directory.
npm install -g @ulpi/lokei && lokei setup