Portainer logo
Control Panels

Portainer Hosting on Your Own VPS

A web interface for Docker — containers, images, volumes and networks, without living in the CLI.

Size a server for Portainer

Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.

2 vCPU
2 vCPU $1.97 a month 64 vCPU
4 GB
4 GB $1.97 a month 128 GB
40 GB
20 GB $1.51 a month 2000 GB

What Portainer is

Portainer is a management interface for container runtimes. It connects to Docker on the same host and gives you containers, images, volumes, networks and stacks in a browser: start and stop things, read logs, open a shell into a container, deploy a Compose file.

It is a viewer and controller, not a platform. Portainer does not package applications or decide how they update — it shows you what Docker is doing and lets you change it. That makes it a good fit when you already work in containers and want the day-to-day operations to be quicker, and a poor fit if what you actually wanted was an app store.

On a VPS the important detail is what access it needs. Portainer talks to the Docker socket, and control of the Docker socket is effectively root on the host. It should be behind TLS with a strong password, and its port should not be open to the internet at large.

“Portainer Community Edition is a free, lightweight container management UI for Docker, Swarm, Podman, Kubernetes, and ACI environments.”

— Portainer, on GitHub

Why run Portainer on a VPS

Full root on the host, so Docker itself is yours to configure.

Run any image from any registry, including private ones.

Firewall control, so the Portainer port can be restricted to your own address.

Size the server for the containers you plan to run, not for Portainer — it is small.

Portainer features

Container lifecycle management with logs and an in-browser shell

Image, volume and network management

Compose stacks deployed from the interface or from Git

Templates for common applications

Role-based access for teams

Registry configuration, including private registries

Resource usage per container

Portainer hosting requirements

The recommended starting point for Portainer, not a hard floor — size it on the sliders.

MemoryPortainer needs little; size for the containers — 4 GB is a realistic start
CPU2 vCPU, again driven by workload rather than by Portainer
Storage40 GB; images and volumes are what consume it
Operating systemUbuntu 22.04 LTS or Debian 12 with Docker
Installs onUbuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13 (Trixie), Debian 12 Bookworm, AlmaLinux 9, AlmaLinux 8, Rocky Linux 9, Rocky Linux 8
Ready inAbout 5 minutes
Smallest server2 vCPU · 4 GB memory · 20 GB disk

How deployment works

Docker is installed on the server and Portainer runs as a container with access to the Docker socket. That access is equivalent to root on the host, so it is served over TLS and the port should be restricted to addresses you control rather than left open.

It is your server. Portainer is installed directly on your VPS or VDS, not inside a container we manage. You get root over SSH, you can install anything alongside it, change its configuration, or remove it entirely. We do not hold a key to it.

What people run it for

Operating a container host

Everyday start, stop, log and shell work without SSH for each step.

Deploying Compose stacks

Push a stack from a Git repository and redeploy on change.

Giving a team limited access

Roles that let someone restart a service without handing over the host.

Running self-hosted apps

A practical front end when everything you self-host is already a container.

Portainer hosting questions

A VPS running Docker with the Portainer web interface, so containers, images, volumes and networks can be managed from a browser.

Deploy Portainer on your own server

Root access, your choice of size, and no container between you and the application.