Container engine

Containers that purr instead of roar.

DoCatz will be the Docker engine and desktop of the family — fast and light on your Mac, quiet when idle, open source, at home on its own and better next to the other cats. Not released yet.

docker compose up · catz-shop · 4 containers running · 0.3 % CPU idle · planned

Coming soonOpen sourceApple silicon firstAI-connected ✦

Watch on GitHub

Docker CLI
Compose
Buildx
containerd
virtiofs
Rosetta
Apple Virtualization
*.docatz.localhost
Volumes
Networks

What is planned

A light engine with a curious cat on top.

A small Linux VM on Apple’s own virtualisation does the heavy lifting; the cat keeps it quiet, quick and out of your way.

The engine

Apple Virtualization (vz) · dockerd + containerd · virtiofs file sharing · Rosetta for amd64 images

Starts in seconds, gives memory back when idle, and your usual `docker` and `docker compose` keep working through the `docatz` context.

Every container on its own name

https://<service>.<project>.docatz.localhost · published ports on localhost · a trusted local CA

.localhost needs no DNS setup; with DevCatz installed DoCatz uses its CA, so every container gets HTTPS without a warning.

The desktop

Containers by compose project · logs · terminal · files · images, volumes and networks · stats · menu bar

See what runs, what it costs and why it stopped — then fix it from the same window.

Moving in

Images · volumes · contexts from the Docker setup you use today

Bring them over, or keep both side by side while you try it.

> why does api keep restarting?

AI, with your containers

Ask why it stopped. The cat reads the logs for you.

The same shared AI connection as the other cats. DoCatz will know your containers, images and the lines that failed, so a crash loop becomes a sentence you understand — with the fix as a button.

Asks before every action
Restarts, rebuilds and edits are buttons you press.
Names and lines, never your env
Container names, states and the log lines you picked — environment values are masked first.
Keys stay in your Keychain
Encrypted by macOS, never in a settings file.
Set the provider once
Claude by default; one setting shared by every Catzoid app.

docatz — ask ⌘Kplanned

why does api keep restarting?

DoCatz

api exits with code 1 a second after start: it cannot reach db:5432 because db is still starting. Add a healthcheck to db and make api wait for it.

api: depends_on: db: condition: service_healthy

Apply to composeShow the logsRestart api

Ask DoCatz (⌘K)

“start shop’s containers”, “free up disk space”

Plain words become steps you run one by one.

Explain a crash

A crash loop, an OOM kill, a failed build

What happened, why, and the change to the Dockerfile or compose file that fixes it.

Write the Dockerfile

From the project’s detected stack

Reviewed as a diff before it is written — the same generator DevCatz uses.

Preview what is sent

Every request, before it goes out

Env values and secrets are masked; suggestions are buttons you click.

Off until you turn it on · one connection, shared with every Catzoid app ·Claude (default)OpenAIGeminiDeepSeekZ.aiMistralxAIGroqOpenRouterOllamaany OpenAI-compatible server

The MCP with the cats insidesoon

MCatzP. em-catz-pee

One MCP server for the whole Catzoid family. Your AI assistant — Claude, Cursor or any other that speaks MCP — will be able to list containers, read their logs and restart a service in DoCatz, and reach the other cats you have installed through the same connection. One connection, every cat — and you hold the keys: only what you allow, nothing runs without you seeing it.

Works with ClaudeGeminiGPTGLM— any app that speaks MCP.

Meet MCatzP