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.
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 -dFree 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.


I'm Sebastián, a Senior Software Engineer. Docker alone wasn't enough for me: it offers no visual customization of networks, and its desktop version is paid, so I couldn't use it at the company where I worked.
I tried Podman and it did not solve the problem either; on the contrary, it brought friction. So I built Nautix: a panel where networks can be seen, moved and connected, and every change can be reviewed and undone.
It's open because it's a shared pain.
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. 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.
Nautix focuses on seeing and editing networks and their connections, and on applying changes with a plan and rollback. It is younger and smaller; Portainer has more enterprise features.
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.