Early Access 🚀 v0.3.0: New Features · Apr 19, 2026

Docker, the
way it should look.

Dockev is the visual way to work with Docker. Manage containers, images, volumes, and networks — without fighting the CLI.

Works with any Docker engine macOS · Linux · Windows
Dockev — Compose Stats
No more manually type
Works with Colima Podman Docker Engine Docker Desktop OrbStack Rancher Desktop Any Docker Socket

New to Docker?

Not sure what
any of this is? Start here.

1
Containers

A container is a lightweight, isolated package that runs a single app or service — your database, your web server, your background worker. It includes everything the app needs, so it runs the same way on any machine.

You don't need to understand the internals. Docker handles the creation and lifecycle of containers automatically — you just decide which ones to run.

The concept
2
Docker

Docker is the engine that creates and runs those containers. It's open-source and used by millions of developers to run apps locally without installing them permanently.

The catch: Docker Engine is a command-line only tool — there's no built-in UI. You type commands to start containers, check logs, and manage everything.

Open-source
3
Dockev

Dockev is a visual interface for Docker Engine. Instead of remembering commands, you get a proper desktop app — a dashboard showing all your containers, buttons to start and stop them, and panels for logs, files, and stats.

Already using Docker Desktop? Dockev works with that too, though Docker Desktop already has its own UI.

That's Dockev

Still have questions? Check the FAQ →

Features

Everything you need, all in one place.

Dedicated views for every part of your container workflow — manage, monitor, and debug without ever touching the terminal.

Make it yours

Customize every detail to match your style and workflow.

Theme Color Schemes
Default
GitHub
One Dark
Dracula
Nord
Tokyo Night
Gruvbox
Rosé Pine
Default
GitHub
One Dark
Dracula
Nord
Tokyo Night
Gruvbox
Rosé Pine
Light
GitHub Light
Solarized
Sandstorm
Rosé Dawn
Gruvbox Light
Catppuccin
Evergreen
Light
GitHub Light
Solarized
Sandstorm
Rosé Dawn
Gruvbox Light
Catppuccin
Evergreen
List Density
Normal
apilanggenius/dify-api:1.13.0
db_postgrespostgres:15-alpine
init_permissionsbusybox:latest
nginxnginx:latest
Compact
api
db_postgres
init_permissions
nginx
plugin_daemon
Roundness
Button
Running
None
Button
Running
Small
Button
Running
Medium
Button
Running
Full
UI Font Size Terminal Font Icon Only Buttons Tab Style more coming soon ...
Why Dockev

Pick the right tool for yourself.

Every Docker tool has a different personality. Here's where each one fits — and where Dockev stands out.

Option 1
lazydocker
Terminal UI for Docker power users
Pick this if
You live in the terminal and want a keyboard-driven TUI to browse containers, logs, and stats without memorizing every Docker flag. Fast, lightweight, and stays out of your way.
The catch: still a terminal app — limited visual feedback, no richer views for Compose, volumes, or networks, and a keybinding learning curve.
Option 2
Docker Desktop
The official all-in-one
Pick this if
You want one download that handles everything — the runtime, a basic GUI, and Kubernetes support. Perfect if you just want it to work out of the box.
The catch: requires a paid subscription for commercial use at companies over 250 employees.
Option 3
Portainer
Enterprise-grade, browser-based
Pick this if
You're managing Docker across multiple servers, teams, or environments, and need access controls, audit logs, and a web UI your whole team can share.
The catch: overkill for a single developer. You need a browser, and setting it up adds complexity to a simple local workflow.
Security

Your credentials
stay on your machine.

Dockev never stores passwords or secrets itself. Engine credentials, remote connection tokens, and TLS keys are handled entirely by your operating system's own secure storage.

macOS Keychain Access System
Linux libsecret / Secret Service System
Windows Credential Manager System
OS keychain integration
When you save a remote connection, Dockev stores credentials using your OS's native secure storage — Keychain on macOS, libsecret on Linux, Credential Manager on Windows. The same place your browser and SSH client store secrets.
No passwords stored by Dockev
Dockev itself holds no credentials. It reads from and writes to the system keychain on your behalf — if you uninstall Dockev, no secrets are left behind in app-specific files or databases.
Encrypted remote connections
Remote engine connections support TLS — you can provide a client certificate, CA certificate, and key for mutual authentication. All traffic between Dockev and a remote daemon is encrypted end-to-end.
Local connections are socket-only
When connecting to a local Docker engine, Dockev communicates via a Unix socket (macOS/Linux) or named pipe (Windows) — no network exposure, no open ports, and the same permissions model Docker itself uses.
Changelog

What's new.

Dockev ships updates regularly. Here's what's landed recently.

See all changelog
Support

Dockev runs on your support.

Built by one developer. Pay what you want — every donation keeps development full-time and independent.

Love Dockev? Help keep it going.
A small tip — pay what you want — goes straight to development and keeps the project moving.
Donate to Dockev
FAQ

Common questions

Anything else? Reach out on GitHub.

Any engine that exposes a Docker-compatible API socket — Docker Desktop, Docker Engine, Colima, OrbStack, Podman, or Rancher Desktop all work the same way. Under the hood they all run a Docker or containerd daemon and expose a socket Dockev can connect to. If docker ps works on your machine, Dockev will too.
On macOS, Docker can't run natively — it needs a Linux VM underneath. Docker Desktop, Colima, OrbStack, and Rancher Desktop all solve this the same way: they spin up a lightweight Linux VM and run Docker inside it. The difference is just how they manage that VM and what license they use. From Dockev's perspective they're identical — it connects to the socket each one exposes and talks the same Docker API regardless.
No — Dockev sits on top of whatever you already have. It's a visual client, not a runtime. Your existing containers, images, volumes, and networks are all still there. You can keep using the terminal alongside Dockev if you want.
Yes. Dockev supports remote connections via TCP — just point it at your remote host's Docker API endpoint. You can manage multiple engine connections (local and remote) and switch between them from the dropdown in the toolbar.
macOS (12 Monterey and later, both Apple Silicon and Intel), Linux (Ubuntu 22.04+ and most modern distros, ships as AppImage), and Windows (10 / 11 with Docker Desktop or WSL 2 + Docker Engine).
Dockev uses Bollard, a Rust Docker API client, to communicate with the Docker daemon via its socket. On macOS and Linux this is a Unix socket; on Windows a named pipe. It's the exact same API the Docker CLI uses — whichever engine you're running, Dockev speaks to it identically.
Dockev is donation-supported. You can use it for both personal and commercial work, and pay what you want to keep development going.
Yes — the Compose manager is included. Load any docker-compose.yml, bring services up or down individually, and monitor the health of your whole stack from one screen.

Stop typing,
start seeing.

Replace terminal commands with a beautiful desktop app that works with the engine you already have.

macOS 12+  ·  Ubuntu 22.04+  ·  Windows 10/11