Self-host Activepieces on a VPS
An open-source, no-code automation tool for connecting apps and building AI-powered workflows.
levelrail-cli templates deploy activepieces --name my-activepiecesSpecification
- Status
- Listed
- Category
- Automation
- Services
- activepieces, db, redis
- Ports
- 80
- Volumes
- 2
- Memory
- about 512 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, MIT
About Activepieces
An open-source, no-code automation tool for connecting apps and building AI-powered workflows. Runs 3 containers (activepieces, db, redis), with activepieces listening on port 80 and keeps its data in named volumes.
What it deploys
Activepieces runs as 3 services in a single Compose app, listening on port 80, with 2 named volume mounts.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| activepieces | ghcr.io/activepieces/activepieces | 0.75.0 | 80 | none |
| db | postgres | 16-alpine | none | activepieces_db_data -> /var/lib/postgresql/data |
| redis | redis | 7-alpine | none | activepieces_redis_data -> /data |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 4 secrets are generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| activepieces | AP_ENCRYPTION_KEY | Generated at deploy |
| activepieces | AP_FRONTEND_URL | Preset by the template |
| activepieces | AP_JWT_SECRET | Generated at deploy |
| activepieces | AP_POSTGRES_DATABASE | Preset by the template |
| activepieces | AP_POSTGRES_HOST | Preset by the template |
| activepieces | AP_POSTGRES_PASSWORD | Generated at deploy |
| activepieces | AP_POSTGRES_USERNAME | Preset by the template |
| activepieces | AP_REDIS_HOST | Preset by the template |
| db | POSTGRES_DB | Preset by the template |
| db | POSTGRES_PASSWORD | Generated at deploy |
| db | POSTGRES_USER | Preset by the template |
Install Activepieces on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get activepieces -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy activepieces --name my-activepieces
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Activepieces.
Docs and upstream
More in Automation
- autobrrMatches torrent releases from your indexers against filters and pushes hits straight to your download client.
- n8nBuild automations and connect your tools with a visual, node-based workflow editor.
- n8n (Postgres)n8n backed by Postgres instead of its default SQLite file, for production workflow volumes.
- Node-REDA flow-based visual editor for wiring together hardware, APIs, and online services.
- PrefectPython-native workflow orchestration with scheduling, retries, and a dashboard for every flow run.
- TemporalDurable workflow execution: write long-running business logic as code and let Temporal survive failures.