Stacks and catalog
More than 350 ready-made services, or your own docker compose.
A stack is a set of containers described by a docker-compose.yaml. Use a stack for ready-made tools, such as n8n, Plausible, WordPress or Supabase, or when your project already has a compose file.
Three ways to create
In a project, click New resource and choose one of the three:
| Option | When to use |
|---|---|
| Catalog service | More than 350 ready-made services. Pier generates passwords and keys and asks only what is needed, such as the domain |
| Custom compose | You paste a docker-compose.yaml into the panel |
| Server folder | The compose file is already in a folder on the server, with the .env and the secret files next to it |
Catalog
Search by name or browse by category. Each service shows what it asks for: domain, e-mail, options.
- All services go through
docker composevalidation. The ones marked verified were also really deployed and checked. The others warn that they have not been tested in a real deploy yet: test before using in production. - Some services ask for special powers over the server: access to the Docker socket, privileged mode, host network or processes, host ports, host folders. The form explains each power and asks you to confirm before creating.
- Services that create the administrator account on their own get a password generated by Pier. When there is no safe way to do this, the service stays private until you finish setting it up.
Custom compose
Paste the compose file and set, for each service that must have a domain, the port and the address. Pier generates values for variables with special names, so you do not leave passwords in the file:
| Variable | What it receives |
|---|---|
PIER_PASSWORD_X | A strong password |
PIER_USER_X | A user name |
PIER_SECRET_X | A long secret |
PIER_HEX_X | A hexadecimal value |
PIER_BASE64_X | A base64 value |
PIER_URL_<SERVICE> | The public address of the service that has a domain |
PIER_HOST_<SERVICE> | The public host of that service |
Replace X with a name of your own. Example: PIER_PASSWORD_DB becomes a password and stays the same in every deploy.
services:
app:
image: ghcr.io/acme/app:2.1.0
environment:
DATABASE_URL: postgres://app:${PIER_PASSWORD_DB}@db:5432/app
PUBLIC_URL: ${PIER_URL_APP}
db:
image: postgres:17-alpine
environment:
POSTGRES_USER: app
POSTGRES_PASSWORD: ${PIER_PASSWORD_DB}
volumes:
- data:/var/lib/postgresql/data
volumes:
data:Images with traefik.* or pier.* labels are refused. Pier takes care of routing.
Server folder
Point to a folder on the machine, for example /srv/loja, that already has the compose file. Pier uses the files where they are:
- the
.env, theenv_filefiles and thesecretsare not copied into the panel; - relative paths keep working;
- to change something, edit the compose file in the folder and deploy again.
If the project already ran by hand, enter the compose project name. This way Pier takes over the same volumes, without losing data.
If Pier runs in a container, the folder must be mounted in it at the same path. In Pier's
compose.yaml, add a line undervolumes, such as- /srv/stacks:/srv/stacks, and run./install.shagain.
Operate a stack
On the stack page:
- Deploy applies the compose file. Services without changes are not recreated.
- Logs and the state of each service sit side by side.
pierctl stack check <name>points out required variables that are missing, before the deploy.- Container logs rotate automatically, so they do not fill the disk.