OrbStack Domains alternative
OrbStack Domains gives containers and Compose services automatic local identities inside the OrbStack runtime. lokei gives the whole development project an identity, whether its services run as host processes, Docker Compose, Laravel Sail, or a mixture of all three.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupOrbStack follows containers; lokei follows the repository and its service model.
Scroll horizontally to see every column.
| Capability | lokei | OrbStack Domains | Official evidence |
|---|---|---|---|
| Primary scope | Host processes, Docker Compose, Laravel Sail, monorepos, and mixed project services | Containers, Compose services, OrbStack Linux machines, and OrbStack Kubernetes | |
| Default name | https://project.test plus service subdomains where needed | container-name.orb.local or service.project.orb.local | |
| Port detection | Allocates and injects ports while starting the application or stack | Probes a container's listening ports on first connection and remembers the HTTP or HTTPS result | |
| Starting the project | lokei run launches the framework command, Compose stack, Sail project, or declared services | Domains appear for containers that are already running in OrbStack; Docker or Compose owns startup | |
| Public sharing | Native project-aware HTTP share sessions with service selection | The container-domain documentation covers local access and does not describe a public tunnel workflow | |
| Container runtime | Works with the installed Docker-compatible environment rather than replacing it | Provides the container and Linux runtime in addition to the domain feature |
The relevant boundary is not Docker support—it is whether every important process lives inside the container runtime.
Scroll horizontally to see every column.
| Capability | lokei | OrbStack Domains | Official evidence |
|---|---|---|---|
| Zero-config container names | Discovers Compose and Sail services when the project is run and assigns public route names | Every running container automatically receives an orb.local name without labels or port publishing | |
| Automatic HTTPS | Trusted certificates are generated for active .test routes by the lokei proxy | Dynamic certificate generation, trust installation, and reverse proxying are built into container domains | |
| Custom domains and wildcards | Supports configured project routes, service subdomains, and a configurable development TLD | Docker labels add custom .local names and wildcards; other custom TLDs are not supported |
Scroll horizontally to see every column.
| Capability | lokei | OrbStack Domains | Official evidence |
|---|---|---|---|
| Compose naming | Uses project configuration and detected service roles to choose public application and service routes | Groups every Compose service as service.project.orb.local based on the Compose project name | |
| Databases and private workers | Keeps databases, caches, queues, and internal workers out of public HTTP routes and share selection | Every container receives a domain; non-HTTP services remain reachable by domain and their service port | |
| Multiple web ports | Declared routes and service configuration disambiguate multiple HTTP applications | Automatic detection chooses a web port; a dev.orbstack.http-port label overrides ambiguous containers |
Scroll horizontally to see every column.
| Capability | lokei | OrbStack Domains | Official evidence |
|---|---|---|---|
| Host-native applications | Runs package scripts and framework commands directly on the host as well as container stacks | Container domains apply to OrbStack containers and related runtime resources, not arbitrary host dev servers | |
| Kubernetes local domains | Different scope: it focuses on project and Compose development services | Provides k8s.orb.local and domains for LoadBalancer and Ingress services in OrbStack Kubernetes | |
| Inspection and replay | Built-in browser inspector for local traffic with bodies, filters, replay, and HAR export | The domain feature documents routing and an index page, not an HTTP capture and replay inspector |
OrbStack's advantage is deep runtime integration; lokei's advantage is a runtime-independent project model.
A remarkably automatic local network for containers.
One project identity across containers and non-container processes.
If the container runtime already defines the whole project, OrbStack is hard to beat. Mixed projects benefit from lokei's wider boundary.
You do not need to replace OrbStack. lokei can use its Docker-compatible runtime while providing project startup, .test routes, inspection, and public sharing.
OrbStack's local HTTPS listener and lokei's proxy may compete for standard ports depending on configuration. Verify port ownership before enabling both HTTPS routing layers.
Answers about automatic container domains, Compose, host processes, ports, and public sharing.
Yes. OrbStack automatically gives containers and Compose services domain names, detects their web ports, and serves them over HTTP or HTTPS. lokei adds value when the workflow also needs project startup, non-container processes, service classification, inspection, or public sharing.
No. OrbStack is a container and Linux runtime. lokei is a development proxy and lifecycle layer that can use OrbStack as the Docker-compatible runtime underneath it.
lokei. OrbStack Domains applies to resources inside OrbStack. lokei can start and route host processes directly and can also wrap Compose or Laravel Sail when the project is containerized.
OrbStack Domains is more automatic once containers are running because every service receives a predictable domain and its web port is detected. lokei is more automatic across the full command lifecycle because it can start the stack and decide which services are public.
Yes. Docker labels add custom .local domains and wildcard names. OrbStack currently limits custom container domains to the .local TLD. lokei uses .test by default and supports a configurable local development TLD.
The reviewed container-domain documentation describes local routing, HTTPS, and an index page, not a built-in public tunnel. lokei share creates a public project session and can share selected HTTP services while excluding private infrastructure.
Yes. OrbStack can remain the container runtime and retain orb.local access while lokei starts the repository and provides .test routes, inspection, and sharing. Check for local HTTPS port conflicts before enabling both proxy layers.
OrbStack claims use its official container-domain documentation. lokei claims use the public website and npm package documentation.
Verified July 16, 2026. OrbStack behavior can change. OrbStack is a trademark of its respective owner. lokei is not affiliated with or endorsed by OrbStack. Claims about absent public sharing or inspection are limited to the reviewed container-domain surface and are worded as undocumented rather than impossible.
$ lokei run
Install lokei and run the whole project through named .test routes while keeping your preferred Docker-compatible runtime.
npm install -g @ulpi/lokei && lokei setup