See your infrastructure.
Networks are boxes and containers live inside. Find out in seconds what can reach what.
Draw your networks, connect your services and apply changes with a safety net. A local panel in a single image.
Free and open source (Apache-2.0). No account, no cloud, no telemetry.
Nautix is a web panel to manage Docker on your own machine or server. Each Docker network is a box and the containers live inside it, with their logo. You drag to move, connect or open a tunnel, and every action shows the equivalent docker command. It works with plain Docker and with Swarm.
Networks are boxes and containers live inside. Find out in seconds what can reach what.
Drag from an app to its database and the connection variable is set. Open a tunnel between networks and only the needed port crosses.
Every change waits in a plan, is applied one at a time and is undone if something fails. You always see the equivalent command.
Ports on 127.0.0.1 only by default, HTTPS included, roles and API tokens. Everything stays on your machine.
Screenshots from the demo engine: names and data are examples.
Container inspector with its networks, ports and actions
Tap the screenshot to enlarge it.
Manage Docker from your browser. One command, no cloud, everything on your machine.
Nautix is a self-hosted web app to manage Docker. It starts with one command, opens at https://localhost:3737 and covers containers, images, volumes, networks, Compose and builds. Every command in docker --help is available as a visual action or in a web terminal.
/folder:/folder mapping from the interface./, sensitive paths) ask for explicit consent with a clear message, and the server rejects any that were not accepted.docker system prune-style cleanup button, with a preview of what will be deleted.127.0.0.1 only.no-new-privileges.Nautix 1.0 is the first public release and it keeps evolving. If something breaks or a feature is missing, your feedback helps decide what comes next.


I'm Sebastián, a Senior Software Engineer passionate about building tools that improve the developer experience.
I found Docker limiting when it came to visualizing and managing networks. I explored alternatives such as Podman, but none of them delivered the experience I was looking for.
That is how Nautix was born, a personal initiative to rethink how we interact with Docker: a panel where networks can be visualized, moved and connected, with the ability to review and undo changes.
I'm sharing it publicly because I believe the best tools shouldn't only solve the problems of the people who build them.
And this is just the beginning. I have an ambitious vision for Nautix: to go beyond a management panel and build an experience that makes working with Docker more visual, friendly and natural.
To manage Docker, Nautix uses the Docker socket. Whoever controls that socket is effectively root on the server. This is true of every Docker panel.
It always requires authentication, publishes the port on 127.0.0.1 only, runs as a non-root user with a read-only filesystem and no extra capabilities, and never shows your secrets.
Don't expose it to the internet; for remote access use a VPN (Tailscale, WireGuard) or a proxy with HTTPS and a second factor. For the strictest setup, run it with rootless Docker.
SECURITY.md · More detail in SECURITY.md
With Docker running, it takes two minutes.
Docker installed and running. On Linux install it directly; on Windows, through WSL2; it also works on Docker Desktop (Windows and Mac) with the same command. Check with docker --version.
Download the Compose file and bring it up.
export NAUTIX_IMAGE=josesebastiangarcia/nautix
export DOCKER_GID=$(stat -c %g /var/run/docker.sock)
curl -fsSLO https://raw.githubusercontent.com/JoseSebastianGarcia/nautix/main/compose.hub.yaml
docker compose -f compose.hub.yaml up -dOpen https://localhost:3737, paste the setup token shown by the command below and create your admin user.
docker compose -f compose.hub.yaml logs nautixThe browser warns about the certificate the first time; follow Settings → HTTPS certificate.
Drag a template (Traefik, Nginx, PostgreSQL…) onto a network box, or create a new network.
Yes. The code is Apache-2.0: you can use, modify and redistribute it. The name and the logo are trademarks of the author (see TRADEMARK.md).
The socket is root-equivalent on the server, as with any Docker panel. Nautix reduces the risk: mandatory authentication, local-only port, non-root, read-only and no capabilities. Read SECURITY.md.
Yes: its own canvas where overlay networks are boxes and services are nodes, with a plan and rollback.
No. No telemetry by default; everything is stored in your nautix-data volume.
It is built around networks: you see them as boxes, connect services by dragging, and every change goes through a plan you can review and undo. All in a single, lightweight image with no external dependencies.
Yes, but don't publish it to the internet. Use a VPN or a proxy with HTTPS and a second factor.
One command, two minutes, and your networks stop being a mystery.