Choose the workflow, not the feature count

No. lokei can replace the everyday workflow of starting a local HTTP application, giving it trusted local HTTPS, inspecting it, and sharing it temporarily. ngrok remains the stronger fit for TCP or TLS endpoints, Kubernetes ingress, production gateways, remote agent management, and advanced traffic policy.

Yes. Portless documents flags that delegate sharing to Tailscale, Tailscale Funnel, or ngrok. lokei instead provides a native project-aware share session through lokei cloud.

No. Public pages cite only public lokei documentation and official public documentation from each competitor. Private repositories are never linked or required.

Slim and LocalCan have the broadest feature overlap because both combine local HTTPS domains with public sharing. Slim is closer as a CLI; LocalCan is closer as a desktop application with a CLI and project files. lokei differs by detecting and starting the project before it routes or shares it.

OrbStack Domains is strongest when the entire project already runs in OrbStack containers. lokei is broader when a repository mixes host processes, Docker Compose, Laravel Sail, workers, and several public HTTP services.

Cloudflare Quick Tunnels and LocalTunnel document immediate public URLs without a product-specific project setup. They still expect an already-running service and a known port; lokei share begins from the project directory and starts the application when needed.

Both can produce named .test sites with local TLS, but Herd is a complete Laravel and PHP environment while lokei is a cross-stack command runner, proxy, inspector, and sharing workflow. The right choice depends on whether runtime management or cross-framework routing is the primary need.