vs OrbStack
OrbStack is an excellent engine choice on Mac. Zashiki Warashi does not compete with it. If OrbStack is your docker, Zashiki is the project house that talks to that docker.
Short answer
OrbStack is a macOS-native container runtime — often chosen as a lighter Docker Desktop replacement. It speaks the Docker API and Compose.
Zashiki Warashi is a localhost project control plane: catalog, start/stop native project commands, peek DB-like Compose services, deep-link to tools you already have.
If your search was “OrbStack vs Docker Desktop,” that comparison is elsewhere. This page answers “where does Zashiki fit?” — on top of OrbStack, not against it.
Side-by-side
| Concern | OrbStack | Zashiki Warashi |
|---|---|---|
| Container runtime | Yes | No |
| Fast Docker-compatible API | Yes | Consumes via CLI |
| Multi-project sidebar for repos | Container/project grouping ≠ app catalog | Machine-local project catalog |
Login-shell npm / fnm start |
Not the product | Yes |
| Compass deep-link from compose mongo | Manual | Built-in peek path |
| Resource usage of the engine | OrbStack’s win | N/A |
Recommended pairing
- Install OrbStack (or Docker Desktop) for containers.
- Install Zashiki from Releases.
- Catalog repos; use Stack peek for DBs; use Start/Stop for app processes.
See also vs Docker Desktop and Compose and databases.
FAQ
Does Zashiki embed OrbStack?
No. Install OrbStack (or Docker Desktop) separately. Zashiki shells out to docker compose using a cached binary path.
Is OrbStack required?
Any engine that provides a working docker compose on your PATH is fine. OrbStack is a common choice on macOS.
Will Zashiki manage OrbStack VMs?
No. VM and engine settings stay in OrbStack.