Activepieces with Docker Compose
Activepieces runs as one image, ghcr.io/activepieces/activepieces, on port 80 inside the container. It needs PostgreSQL, Redis, a 32-character hex AP_ENCRYPTION_KEY, an AP_JWT_SECRET and AP_FRONTEND_URL set to the public URL. The first account you sign up becomes the platform admin. After that, new users can only join by invitation.
Activepieces is an open-source automation tool, similar to Zapier. You build flows from triggers and steps in the browser.
If you're new to Docker Compose, check out our guide on how to self-host a Docker Compose app. More stacks are in our Docker Compose library.
Self-host Activepieces with Docker Compose (minimal)
services:
activepieces:
image: ghcr.io/activepieces/activepieces:0.92.3
ports:
- "8080:80"
environment:
AP_ENVIRONMENT: prod
AP_FRONTEND_URL: http://localhost:8080
AP_ENCRYPTION_KEY: changeme_32_hex_characters_here0
AP_JWT_SECRET: changeme_long_random_string
AP_EXECUTION_MODE: UNSANDBOXED
AP_POSTGRES_HOST: postgres
AP_POSTGRES_PORT: 5432
AP_POSTGRES_DATABASE: activepieces
AP_POSTGRES_USERNAME: postgres
AP_POSTGRES_PASSWORD: changeme
AP_REDIS_HOST: redis
AP_REDIS_PORT: 6379
volumes:
- activepieces-cache:/usr/src/app/cache
depends_on:
- postgres
- redis
restart: unless-stopped
postgres:
image: pgvector/pgvector:0.8.0-pg14
environment:
POSTGRES_DB: activepieces
POSTGRES_USER: postgres
POSTGRES_PASSWORD: changeme
volumes:
- postgres-data:/var/lib/postgresql/data
restart: unless-stopped
redis:
image: redis:7
volumes:
- redis-data:/data
restart: unless-stopped
volumes:
activepieces-cache:
postgres-data:
redis-data:
Generate the two secrets before the first start:
openssl rand -hex 16 # AP_ENCRYPTION_KEY (32 hex characters)
openssl rand -hex 32 # AP_JWT_SECRET
docker compose up -d
Open http://localhost:8080 and sign up. That first account is the admin.
AP_ENCRYPTION_KEY encrypts the credentials of your connections (API keys, OAuth tokens). Keep it stable. If it changes, Activepieces cannot read the saved connections, and you must reconnect every app.
AP_FRONTEND_URL must be the URL users open in the browser. Activepieces builds webhook URLs and OAuth redirect URLs from it. A wrong value breaks webhook triggers and app logins. Older guides call this variable AP_PUBLIC_URL.
Deploy Activepieces on Hostim.dev (One-Click)
Activepieces is an open-source automation platform. With Hostim.dev, you can deploy it with Docker, managed PostgreSQL and Redis in one click, with a domain and HTTPS.
Guest project runs for 1 hour. Log in to save and extend to 5 days.
Why Host Activepieces on Hostim.dev?
- One-click Docker deployment
- Managed PostgreSQL and Redis, no setup required
AP_ENCRYPTION_KEYandAP_JWT_SECRETgenerated per deployAP_FRONTEND_URLset to your domain, so webhooks work- Automatic HTTPS and domain
- Real-time logs and metrics
What's included
| Resource | Details |
|---|---|
| App | ghcr.io/activepieces/activepieces:0.92.3 (Community Edition) |
| Database | Managed PostgreSQL |
| Cache | Managed Redis (job queue) |
| Volume | /usr/src/app/cache |
| Secrets | AP_ENCRYPTION_KEY, AP_JWT_SECRET generated per deploy |
| Workers | AP_WORKER_CONCURRENCY=1, one flow run at a time per worker |
| Domain | Free *.hostim.dev subdomain |
| SSL | Let's Encrypt (auto-enabled) |
| Port | 80 |
How to Deploy
- Go to your Hostim.dev dashboard.
- Click Create Project → Use a Template.
- Select Activepieces.
- Choose a resource plan.
- Deploy. The first start takes about two minutes.
- Open your app's domain and sign up. The first account is the admin.
If you add a custom domain later, change AP_FRONTEND_URL to it and redeploy. Webhook URLs follow this value.
FAQ
Frequently asked questions
Which environment variables does Activepieces need?
AP_ENCRYPTION_KEY (32 hex characters), AP_JWT_SECRET, AP_FRONTEND_URL, the AP_POSTGRES_* connection settings and AP_REDIS_HOST / AP_REDIS_PORT. The Hostim template sets all of them.
Does Activepieces need PostgreSQL and Redis?
Yes, for a production setup. PostgreSQL stores flows, runs and connections. Redis is the job queue for flow runs and polling triggers.
Who can sign up on a self-hosted Activepieces?
Only the first person. The first sign-up becomes the platform admin. Every later sign-up fails with INVITATION_ONLY_SIGN_UP until the admin invites that user. We checked this on the Community Edition, version 0.92.3.
What happens if I change AP_ENCRYPTION_KEY?
Saved connections stop working. The key encrypts their credentials, and Activepieces cannot decrypt them with a new key. Set it once and keep it.
Why do my webhook triggers not fire?
Check AP_FRONTEND_URL. Activepieces builds webhook URLs as AP_FRONTEND_URL + /api/v1/webhooks. If the value is localhost or an old domain, outside services call the wrong address.
How much memory does Activepieces need?
Plan for 2 GB for one container that runs the API and the worker. In our test on version 0.92.3, it used about 1 GB after a few flow runs. With a 1 GB limit and the default AP_WORKER_CONCURRENCY=5, the container was killed for lack of memory on the first run. The Hostim template uses 2 GB and AP_WORKER_CONCURRENCY=1.
How long can a flow run?
600 seconds by default (AP_FLOW_TIMEOUT_SECONDS). Longer jobs are stopped.
How do I back up and update Activepieces?
Back up the PostgreSQL database and keep a copy of AP_ENCRYPTION_KEY. Without the key, a database backup cannot restore your connections. To update with Docker, change the image tag and run docker compose up -d. On Hostim.dev, change the image tag of the app and redeploy. Migrations run on start.
Alternatives
- n8n: more nodes and a bigger community. Its Sustainable Use License limits some commercial uses.
- Node-RED: flow-based tool, strong for IoT and devices.
- Zapier and Make: hosted, no server to run, priced per task.
Source + Docs
Looking for something else? Browse all templates →