Expose alternative
Expose is a PHP-first tunnel with managed and self-hosted networks, stable public naming, and strong request inspection. lokei owns the local project workflow before the tunnel: it starts the app, creates trusted local HTTPS, understands its services, and shares them as one project session.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupBoth can infer context from a folder, but they infer different things from it.
Scroll horizontally to see every column.
| Capability | lokei | Expose | Official evidence |
|---|---|---|---|
| Current-directory behavior | Detects the project, starts its normal command or services, and registers its local route | Assumes the current folder is reachable as foldername.test, or accepts an explicit local URL | |
| Local HTTPS ownership | Creates and serves trusted local .test routes itself | Can tunnel an existing local HTTP or HTTPS site but does not create that local site environment | |
| Public tunnel network | Managed lokei cloud share sessions tied to project and service identity | Managed Expose network or a self-hosted Expose server | |
| Public naming | Stable project-based names, requested vanity subdomains, and custom domains through lokei cloud plans | Slug-derived or chosen subdomains, reserved subdomains, and white-label custom domains | |
| Traffic inspection | Local browser inspector with filtering, editable replay, retention, and HAR export | CLI and web dashboard show incoming requests and support inspection and replay | |
| Application lifecycle | Starts frameworks, Compose, Sail, and declared services before sharing | Tunnels an already-reachable site or local URL; the application environment is supplied separately |
Expose has the edge when relay deployment control matters. lokei has the edge when the tunnel must be part of a complete local project lifecycle.
Scroll horizontally to see every column.
| Capability | lokei | Expose | Official evidence |
|---|---|---|---|
| Herd and Valet integration | Can run Laravel directly or detect Laravel Sail without requiring Herd or Valet | The no-argument folder workflow is designed around the .test convention used by Herd and Valet | |
| Framework breadth | Detects 30+ frontend and backend stacks and their expected environment variables | Can tunnel any reachable HTTP or HTTPS site but its CLI and ecosystem are PHP-first | |
| Docker and multi-service startup | Discovers Compose and Sail, starts dependencies, and distinguishes public services from private infrastructure | Can tunnel a container or service URL but does not own its Compose or dependency lifecycle |
Scroll horizontally to see every column.
| Capability | lokei | Expose | Official evidence |
|---|---|---|---|
| Managed service | Hosted sharing is integrated with lokei project sessions and account authorization | Expose offers a managed free and Pro network with regions, reserved subdomains, and team features | |
| Self-hosting | The customer-facing sharing service is managed by lokei | The Expose server can be hosted on your own infrastructure for data and domain control | |
| Custom domains | Supports custom-domain capabilities through lokei cloud plans | Managed Pro or self-hosted servers can use owned domains and automatic SSL |
Scroll horizontally to see every column.
| Capability | lokei | Expose | Official evidence |
|---|---|---|---|
| Where inspection runs | Normal local traffic and public-share traffic can be inspected through the local lokei interface | The Expose CLI and dashboard inspect requests passing through an Expose tunnel | |
| Multi-service session | One project share can include selected web, API, and documentation services with consistent names | Each share command targets a site or URL; several services are coordinated as separate tunnel connections | |
| Start before share | A stopped project is started and checked before the share session succeeds | The local site must already be reachable through its inferred .test name or supplied URL |
Expose offers more tunnel deployment control; lokei offers more control over the application lifecycle behind the tunnel.
A flexible PHP-friendly tunnel that can be managed or self-hosted.
One cross-stack command from stopped project to local and public URLs.
Choose based on whether tunnel deployment control or project lifecycle automation is more important.
Keep Expose available for self-hosted or white-label requirements while evaluating lokei as the project runner and default share command.
This staged approach avoids breaking registered webhook or OAuth domains while you compare the local startup and inspection workflows.
Answers about Laravel, local HTTPS, self-hosting, custom domains, inspection, and multi-service shares.
No. Expose can tunnel any HTTP or HTTPS site reachable from the machine. Its current-directory conventions, PHP implementation, and Herd or Valet integration make it especially natural for Laravel and PHP developers.
No. Its no-argument folder workflow assumes the site is already reachable through a foldername.test convention, usually from Herd or Valet. lokei creates the named local HTTPS route and starts the application itself.
Yes. Expose inspects and replays traffic passing through its tunnel in the CLI and dashboard. lokei inspects routed local and shared traffic through a browser interface and adds filtering, editable replay, retention, and HAR export.
Expose documents a self-hosted server and is the stronger choice when relay infrastructure must run in your account. lokei's customer-facing sharing service is managed, while its local proxy, DNS, certificates, and inspector run on the developer machine.
lokei. It detects and starts the Sail or Compose stack and distinguishes public HTTP services from databases, caches, and workers. Expose can tunnel the resulting URL or port once that stack is already reachable.
Expose is stronger when white-label domains and self-hosted infrastructure are requirements. Both products offer managed custom-domain capabilities, but Expose explicitly supports owned domains on Pro and self-hosted servers.
lokei. It can model dependencies and share selected HTTP services under one project session and naming scheme. Expose can open separate tunnels to each URL, but service discovery and lifecycle coordination remain external.
Expose claims use its official product, client sharing, custom-domain, and self-hosting documentation. lokei claims use the public website and npm package documentation.
Verified July 16, 2026. Managed plans, regions, and features can change. Expose is a trademark of its respective owner. lokei is not affiliated with or endorsed by Expose. Claims about current-folder inference are limited to Expose's documented Herd and Valet-style .test convention.
$ lokei run
Install lokei, complete setup once, and run or share an existing project from its folder across frameworks.
npm install -g @ulpi/lokei && lokei setup