Activepieces: Open-Core alternative to Zapier in 2026
Activepieces is a workflow automation platform with 200+ integrations and a visual no-code builder, built as a modern open source alternative to Zapier or Make.
Core is open source, but advanced features or enterprise support may be behind a paid tier β check the license.
Audit Snapshot
View notes βLicense β Not verifiable on GitHub
GitHub β Active
Latest release β 0.92.3 Β· today
Docker Compose β Partial
Production β Not production-tested by AltFreeStack
Activepieces vs. Zapier
Pros
- Noticeably more modern interface than n8n's
- MIT-licensed core
Things to consider
- Some team features (SSO, analytics) are Enterprise-only paid add-ons
- Integration ecosystem still smaller than Zapier's
Quick Docker installation guide
Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide β
π‘ Official SaaS or self-hosted with AltFreeStack?
- On the official cloud: $19.99/mo on Zapier.
- On your own VPS: the core is free to self-host on your own server β no more monthly SaaS fee, though some advanced features stay behind a paid plan.
services:
activepieces:
image: activepieces/activepieces:0.92.1
restart: unless-stopped
ports:
- "8080:80"
environment:
AP_ENCRYPTION_KEY: change-me-32-char-key # REQUIRED: generate a random secret before first run
AP_JWT_SECRET: change-me-super-secret # REQUIRED: generate a random secret before first run
AP_FRONTEND_URL: http://localhost:8080 # CHANGE THIS TO YOUR DOMAIN
AP_POSTGRES_HOST: activepieces-db
AP_POSTGRES_USERNAME: activepieces
AP_POSTGRES_PASSWORD: change-me-postgres-password # REQUIRED: generate a random secret before first run
AP_POSTGRES_DATABASE: activepieces
AP_REDIS_HOST: activepieces-redis
depends_on:
- activepieces-db
- activepieces-redis
activepieces-db:
image: postgres:15-alpine
restart: unless-stopped
environment:
POSTGRES_USER: activepieces
POSTGRES_PASSWORD: change-me-postgres-password # must match AP_POSTGRES_PASSWORD above
POSTGRES_DB: activepieces
volumes:
- activepieces_pg_data:/var/lib/postgresql/data
activepieces-redis:
image: redis:7-alpine
restart: unless-stopped
volumes:
activepieces_pg_data:
π Deploy in 1 command
Recommended for beginnersCopy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything β no nano, no pasting code blocks.
curl -sSL ".../api/deploy?stack=activepieces" -o deploy.sh && cat deploy.sh && bash deploy.shThis docker-compose corresponds to an actively maintained project β last commit today.
This docker-compose not working for you? Report it on GitHub βTechnical profile
- License
- MIT
- Category
- Dev Tools
- Replaces
- Zapier, Make
- Tech stack
- Node.jsPostgreSQLRedisReact
Under the hood
Database
PostgreSQL
Language
TypeScript (Node.js)
Platforms
Web
Key features
- 200+ ready-to-use integrations (pieces)
- Visual no-code flow builder
- SDK to build your own pieces/integrations
Preview

Public image provided by Activepieces on its own website.
πΎ Backups in 3 steps (Day 2)
As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update β that's the only thing you need to back up.
1. Create a compressed backup on the server
tar -czvf backup-$(date +%F).tar.gz ./data2. Download it to your computer
From your computer's terminal (not your server's):
scp root@YOUR_IP:~/app/backup-*.tar.gz ./3. Restore in case of emergency
tar -xzvf backup-file.tar.gzπ Connect your domain with free SSL
Step 1 β Set up the DNS
In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:
- Type
- A
- Name/Host
- @ (root domain) or a subdomain, e.g. app
- Content/Value
- Your server's public IP
Wait 5 to 15 minutes for the record to propagate across the internet.
Step 2 β Automatic reverse proxy with Caddy
One single file, no Nginx config or manual certificates β Caddy issues and renews Let's Encrypt HTTPS on its own.
Create a file called Caddyfile:
yourdomain.com {
reverse_proxy localhost:8080
}Start Caddy with this command (pulls the image and runs it in the background):
docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy