Self-host Activepieces with Levelrail

An open-source, no-code automation tool for connecting apps and building AI-powered workflows.

  • Authoractivepieces
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services3

How to self-host Activepieces

  1. Pull the images

    3 images are pulled on your server.

    Show images
    • ghcr.io/activepieces/activepieces:0.75.0
    • postgres:16-alpine
    • redis:7-alpine
  2. Create the app

    3 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    4 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Activepieces requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Activepieces. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Activepieces docs page.

Deploy Activepieces your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Activepieces from the CLI

levelrail-cli templates deploy activepieces --name my-activepieces

Deploy Activepieces with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/activepieces/deploy

Activepieces configuration

Activepieces services

ServiceImagePortsVolumes
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

Activepieces environment variables

VariableServiceValue
AP_ENCRYPTION_KEY activepieces Generated at deploy
AP_FRONTEND_URL activepieces Preset by the template
AP_JWT_SECRET activepieces Generated at deploy
AP_POSTGRES_DATABASE activepieces Preset by the template
AP_POSTGRES_HOST activepieces Preset by the template
AP_POSTGRES_PASSWORD activepieces Generated at deploy
AP_POSTGRES_USERNAME activepieces Preset by the template
AP_REDIS_HOST activepieces Preset by the template
Show all 11 variables
  • POSTGRES_DBdbPreset by the template
  • POSTGRES_PASSWORDdbGenerated at deploy
  • POSTGRES_USERdbPreset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: activepieces_db_data -> /var/lib/postgresql/data, activepieces_redis_data -> /data

Activepieces FAQ

How much memory does Activepieces need?

The catalog lists about 512 MiB of memory for Activepieces across its 3 services.

Does Activepieces run on arm64?

For Activepieces, an arm64 image is published; amd64 is image published.

What licence is Activepieces under?

Activepieces is licensed under MIT, which is permissive, with few conditions on reuse.

Does Activepieces need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Activepieces bundle?

The template includes Postgres and Redis, running as its own service.

Which ports does Activepieces use?

Activepieces listens on port 80 inside the stack.

Where does Activepieces keep its data?

In named volumes: activepieces_db_data mounted at /var/lib/postgresql/data and activepieces_redis_data mounted at /data.

Can I deploy Activepieces on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id activepieces for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/activepieces/activepieces:0.75.0, postgres:16-alpine, redis:7-alpine is what you deploy there.

levelrail-cli templates deploy activepieces --name my-activepieces