ngrok alternative for local development
lokei and ngrok can both make a local HTTP application reachable, but they begin on opposite sides of the boundary: lokei starts with the project on your machine; ngrok starts with ingress from the public network.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupThe products overlap at temporary HTTP sharing, not across their full scope.
Scroll horizontally to see every column.
| Capability | lokei | ngrok | Official evidence |
|---|---|---|---|
| Primary job | Run local development projects behind trusted named HTTPS | Provide globally distributed ingress to services running anywhere | |
| Starting command | lokei run discovers and starts the current project | ngrok http <port> connects to an already-running local service | |
| Local HTTPS domain | Built-in trusted .test domain before anything is shared | Provides a public HTTPS endpoint that forwards to a local port | |
| Traffic inspection | Local capture, filtering, editable replay, and HAR export | Local agent inspector plus cloud inspection, replay, search, and retention | |
| Protocols | HTTP application development and public HTTP sharing | HTTP, HTTPS, TCP, and TLS endpoints | |
| Production ingress | Different scope: local development and temporary sharing | API gateway, Kubernetes ingress, identity-aware proxy, and load balancing | |
| Cost and account model | Local development is free without an account; hosted sharing has free and paid plans | The Free plan requires an account and includes limited one-time usage credit, endpoints, transfer, and requests |
“Different scope” marks capabilities that belong to ngrok's production ingress platform rather than lokei's local-development job.
Scroll horizontally to see every column.
| Capability | lokei | ngrok | Official evidence |
|---|---|---|---|
| Named local domains | Built in with local DNS, a trusted CA, and a configurable local TLD | Not the primary job; the agent forwards a local port to a public endpoint | |
| Application startup | Detects and starts the current framework or configured service | Expects an upstream service address or port | |
| Framework and environment injection | Built in for 30+ development stacks and common application URL variables | Framework-neutral tunnel to the supplied upstream | |
| Docker and multi-service projects | Discovers public Compose and Sail services and models project dependencies | Can expose multiple configured endpoints but does not own the application lifecycle |
Scroll horizontally to see every column.
| Capability | lokei | ngrok | Official evidence |
|---|---|---|---|
| Temporary public HTTPS | Native lokei share session for the current project or selected HTTP services | Core tunnel workflow with an automatically provisioned public HTTPS endpoint | |
| Start before sharing | Starts a stopped project through its normal framework, Docker, or Sail lifecycle | Connects to the upstream supplied by the user | |
| Request replay | Editable replay runs from the local inspector | Local and cloud inspectors support replay; cloud full capture enables retention and search | |
| Access control | Passwords and bearer tokens for shared development URLs | Traffic Policy supports authentication, identity, rate limits, request controls, and more |
Scroll horizontally to see every column.
| Capability | lokei | ngrok | Official evidence |
|---|---|---|---|
| TCP and TLS endpoints | Different scope | Built in for databases, remote access, TLS passthrough, and other network services | |
| Kubernetes ingress | Different scope | Dedicated Kubernetes Operator with Ingress and Gateway API support | |
| Production gateway | Different scope | Traffic Policy, endpoint pools, identity controls, and production API ingress | |
| Remote agent management | Local service lifecycle only | Remote stop, restart, and upgrade operations through API or dashboard |
The honest answer depends on whether the primary problem is local development or public ingress.
A mature ingress and connectivity platform extending far beyond localhost sharing.
A local-first workflow that understands the project before it creates a public URL.
Use the narrower tool for the local job and the broader platform when the network requirements demand it.
You do not need to remove ngrok. Move the project startup and local HTTPS workflow to lokei, then keep ngrok wherever its broader network features are required.
This is a scoped workflow change, not a recommendation to replace ngrok infrastructure that serves production or non-HTTP traffic.
Direct answers about the overlap and the product boundary.
For local HTTP application development and temporary sharing, it can be. It is not a replacement for ngrok's TCP or TLS endpoints, Kubernetes Operator, production gateway, remote management, or advanced Traffic Policy.
Yes. Run lokei share from the project directory. lokei resolves the active project or service, starts it when needed, and creates the public share session.
Both can expose an HTTP webhook endpoint and replay captured requests. Choose lokei when the webhook belongs to a project you also want to start and run behind named local HTTPS. Choose ngrok when you need its cloud retention, policy, team observability, or gateway features.
Yes. lokei can own local project startup and HTTPS while ngrok remains available for infrastructure and protocols outside lokei's scope.
No. lokei's sharing workflow is for public HTTP applications. Use ngrok when you need TCP, TLS passthrough, databases, SSH, RDP, or another non-HTTP protocol.
lokei is designed to understand project services and their declared dependencies, so it can share one service or a coherent group without exposing private workers or databases. ngrok can run several endpoints, but you configure their upstream addresses and lifecycle separately.
ngrok is the relevant option when the requirement is production ingress, a Kubernetes gateway, traffic policy, or globally managed endpoints. lokei is intentionally scoped to local development and temporary collaboration rather than production serving.
Competitor claims use ngrok's official documentation and pricing page. lokei claims use the public website and published npm package documentation.
Verified July 16, 2026. Product capabilities, limits, and pricing can change. ngrok is a trademark of its respective owner. lokei is not affiliated with or endorsed by ngrok. This comparison limits replacement claims to local HTTP development and temporary sharing.
$ lokei run
Install lokei, run the one-time setup, and start the current project without looking up its port.
npm install -g @ulpi/lokei && lokei setup