Slim alternative
Slim and lokei both combine named local HTTPS with public sharing. The practical difference is the starting point: Slim maps a name to a port, while lokei begins with the project directory and owns the process lifecycle around that route.
Last verified: July 16, 2026
npm install -g @ulpi/lokei && lokei setupThese are the differences that change the daily command you run.
Primary input
Default local URL
Starting the application
Project configuration
Public sharing
Request debugging
| Capability | lokei | Slim | Official evidence |
|---|---|---|---|
| Primary input | The current project directory and its detected or declared development lifecycle | A route name and local port, or services declared in .slim.yaml | |
| Default local URL | https://project.localhost on native Windows or https://project.test on macOS, Linux, and WSL2, with trusted TLS | https://name.test with trusted TLS and a hosts-file mapping | |
| Starting the application | Detects and starts the framework, script, Compose stack, Sail project, or configured services | Waits for the explicitly mapped upstream port; --wait can wait for that upstream to become ready | |
| Project configuration | lokei.yaml models commands, HTTP services, dependencies, workers, routes, health checks, and sharing context | .slim.yaml models domains, ports, path routes, custom TLDs, and logging | |
| Public sharing | lokei share resolves and starts the active project, can select services, and supports requested subdomains, passwords, access tokens, TTLs, and custom domains by plan | slim share maps one explicit port and supports requested subdomains, passwords, TTL expiry, and custom domains | |
| Request debugging | Captures request and response bodies with filtering, editable replay, retention, and HAR export | Provides live access logs with full, minimal, or disabled log modes |
Both products solve local HTTPS and sharing. This table separates explicit port routing from project-aware lifecycle management.
Certificate setup
Custom local TLDs
Path routing and service domains
| Capability | lokei | Slim | Official evidence |
|---|---|---|---|
| Certificate setup | One-time setup installs a local CA; certificates are issued for active routes | First run creates a local CA, trusts it, and issues per-domain certificates | |
| Custom local TLDs | Supports one configurable machine-wide local TLD, defaulting to .localhost on native Windows and .test on macOS, Linux, and WSL2 | Accepts .test, .loc, .dev, or another TLD per mapped domain | |
| Path routing and service domains | Can route services by subdomain and declare path routes inside a project model | Maps a domain to a main port and can route paths such as /api to other ports |
Framework awareness
Monorepos and dependencies
Docker Compose and Laravel Sail
| Capability | lokei | Slim | Official evidence |
|---|---|---|---|
| Framework awareness | Detects 30+ stacks and injects the host, port, and common application URL variables | Documents HMR compatibility for tools such as Next.js and Vite but routes the supplied port | |
| Monorepos and dependencies | Models several public services, private processes, dependencies, and health checks as one project | Registers every service mapping listed in .slim.yaml and tears those mappings down together; upstream commands remain external | |
| Docker Compose and Laravel Sail | Discovers and starts Compose or Sail, assigns ports, and exposes only shareable HTTP services | Can route any reachable container port, but Compose and Sail discovery are not documented as built-in lifecycle features |
Zero-argument sharing
Share lifecycle
Diagnostics and health
| Capability | lokei | Slim | Official evidence |
|---|---|---|---|
| Zero-argument sharing | Run lokei share inside the configured project; no route or port is required for a single-service app | The documented share command requires --port and optionally accepts a subdomain, password, or TTL | |
| Share lifecycle | Tracks a project share session with status, service additions, targeted or all-service stop commands, password or token protection, and TTL control | Creates a public mapping for the selected port with subdomain, password, TTL, and custom-domain controls | |
| Diagnostics and health | Provides machine diagnostics plus project and service health information | Provides slim doctor, upstream health status in slim list, and optional readiness waiting |
This is the closest overall comparison. The real differences are distribution, per-route control, project lifecycle, and inspection—not share controls both products already provide.
A source-available, self-contained Go tool for direct network mappings.
A project-aware workflow before and after the reverse proxy.
Choose the smallest ownership model that removes the work you actually repeat.
You can keep .slim.yaml while evaluating lokei, but both default proxies expect to own ports 80 and 443.
Do not run both products on their default proxy ports at the same time. The project source itself does not need to be rewritten for this evaluation.
Direct answers about two products with unusually broad feature overlap.
It is the closest CLI alternative in overall feature shape because it combines named local HTTPS, project configuration, HMR support, diagnostics, logs, and public sharing. lokei goes further into application discovery and lifecycle; Slim stays closer to explicit domain and port mappings.
Yes. Both install a local certificate authority and serve named .test domains over HTTPS. Slim maps names through the hosts file and also accepts other TLDs per route; lokei uses local DNS and one active machine-wide development TLD.
lokei detects and starts the project command. Slim documents HMR compatibility and can wait for the upstream, but its route command maps the name to a port rather than discovering and launching the application command.
Yes. Both support requested public subdomains, password protection, TTL controls, and custom-domain options. The difference is context: Slim shares an explicit port, while lokei resolves the active project or selected services, starts a stopped project, and manages them as one share session.
lokei. Slim documents live access logs and log modes. lokei captures request and response bodies and adds filtering, editable replay, retention controls, and HAR export.
Yes, when services and ports are declared in .slim.yaml. lokei additionally models commands, dependencies, private workers, health checks, Docker Compose, Laravel Sail, and selective multi-service sharing.
Yes, but do not run both default HTTPS proxies simultaneously because both need port 443. Stop one daemon before starting the other.
Slim claims use its public product reference and official source repository. lokei claims use the public website and published npm package documentation.
Verified July 16, 2026. Product behavior can change. Slim is a trademark of its respective owner. lokei is not affiliated with or endorsed by Slim. Where Slim's public reference does not document a lifecycle feature, this page says so instead of claiming the feature cannot exist.
$ lokei run
Install lokei, complete the one-time machine setup, then run it from the project directory.
npm install -g @ulpi/lokei && lokei setup