Containers under control.
Create, start, and monitor Docker containers without the terminal. Statuses, volumes, synchronization — all in one interface.
- 7 days free
- No card required
- Payment in rubles
postgres:16redis:7.2-alpinemetabase/metabasen8nio/n8ndocker inspect postgres
- 1form
- image, ports, environment variables and volumes — on one screen
- 4
- restart policies: no, always, on-failure and unless-stopped
- 7
- container states, exactly as Docker reports them
- 15min
- between syncs of the container and volume lists with the server
Manage
The whole container lifecycle — in one list.
Every container operation — without a single command in the terminal. Each one is a task with a log: you see exactly what ran on the server.
The panel shows the state Docker itself reports: you see which container is running, which one exited and which one is stuck restarting.
- created
- running
- paused
- restarting
- removing
- exited
- dead
-
Installing Docker
Docker is one of the server packages. Install it with a button — when creating the server or later — and it shows up in the services list with autostart.
-
Lifecycle
Create, start, stop, restart and delete containers in one click.
-
Tasks with a log
Every action is a task in the operations center: which Docker command ran and what it returned. While a task is running, the container is locked for other actions.
Panel
Create a container right in the copy of the panel.
The tour runs with captions, like a video with subtitles: the container list, the form, the launch. Click in the window at any moment and carry on yourself.
Configuration
Instead of a long command — form fields.
The panel builds the command itself: it pulls the image, starts the container with your ports, variables and volumes, and remembers the settings — so later you change them instead of recalling them.
Image, ports and variables — in one form
Fill out the form — the container will be created and started on the server. MTProxy has a ready-made template.
- Support for Docker Hub and public images
- Host:container port mapping
- Restart policy: no, always, unless-stopped, on-failure
- Custom start command
- Environment variables and volumes — one entry per line
Runtime options
MTProxy without the long run command
The catalog has one template for now, MTProxy for Telegram. You set the host and port, and the panel prepares the run command, publishes the port and attaches a data volume.
- Host, ports and worker count are set as form fields
- The secret is generated with a button, random padding is switched on in the same form
- The tg://proxy link is ready before the container starts
- Template settings stay available when you edit the container
Telegram link
tg://proxy?server=proxy.example.com
&port=443
&secret=dd9f2c4e1a…c5e3
A new image version — without recreating by hand
Change the image tag, a port or a variable — the panel pulls the image, removes the old container and starts a new one with the same settings.
- Ports, variables and volumes are prefilled in the form
- Named volumes and their data stay on the server
- Every recreation step is visible in the task log
What the panel will do
- Pull the imagedocker pull
- Remove the old onedocker rm -f
- Start the new onedocker run
Data outlives the container
Create a named volume and attach it to a container — the database, uploads or cache stay on the server even if the container is deleted or recreated.
- Create and delete volumes from the panel
- Driver and mount point — in the list
- A container mounts a volume by name or a server directory
- A volume created outside the panel appears after the next sync
Domain and SSL
A domain for the container, with Nginx and SSL.
Publish the container port on 127.0.0.1 only and create an “Application” site: Nginx accepts requests for the domain and passes them to that port. A Let's Encrypt certificate is issued in one click.
- The container port is closed from outside — only Nginx faces the internet
- Let's Encrypt SSL certificate with auto-renewal
- Basic Auth and security headers — like any other site
- Health checks every 5 minutes — like the rest of your sites
Synchronization
Started outside the panel — the container is still in the list.
Every 15 minutes Deploykin syncs containers and volumes with what actually exists on the server. Whatever was started over SSH, from CI or through MCP appears in the panel; whatever was removed disappears.
- Synced via docker ps -a and docker volume ls — every 15 minutes
- Start, stop, restart and delete work for those containers too
- The status is the one Docker reports: from running to dead
- Through MCP, AI can run a container too: the create_docker_container tool
~$ docker run -d --name mq nats:2
8c1f4a92e07b
In the panel 203.0.113.21 Connect done in 4 min 52 s
Run your first container without the terminal.
Manage containers from the panel. Statuses, volumes, and synchronization — everything's ready.
- 7 days free
- No card required
- Human support