Stacks / Automation
Easy
Activepieces + Postgres
Apache-2.0 Zapier alternative: Activepieces with Postgres and Redis.
The problem
Zapier and Make meter every run. If you want a fully open-source pieces model instead of n8n's fair-code license, Activepieces is the other box.
Replaces
Zapier / Make
Estimated SaaS saved
$2,400
per year, small team, before lock-in
One-click template from github.com/9o4t/activepieces: official ghcr.io/activepieces/activepieces + Railway Postgres and Redis. Template generates AP_ENCRYPTION_KEY and AP_JWT_SECRET, wires AP_FRONTEND_URL. No operator API keys. n8n is a separate template at /stacks/n8n-automation.
The stack
- Activepieces
Open-source Zapier alternative
- Postgres
Flows, runs, and connections
- Redis
Job queue (required)
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Make Pro / Teams | $2,400 | Activepieces + Postgres + Redis |
| Zapier Professional (team) | $3,600 | Same box, or /stacks/n8n-automation |
Agent setup prompt
Deploy self-hosted Activepieces that replaces Zapier/Make. Use the official ghcr.io/activepieces/activepieces image plus Postgres and Redis. Do not combine n8n in this project — that is a separate stack at /stacks/n8n-automation. - One container, AP_CONTAINER_TYPE=WORKER_AND_APP, AP_PORT=$PORT. - Set AP_FRONTEND_URL to the Railway public https domain. - Generate AP_ENCRYPTION_KEY (openssl rand -hex 16) and AP_JWT_SECRET (openssl rand -hex 32). Back them up. - Wire AP_POSTGRES_URL and AP_REDIS_URL. Health check GET /api/v1/health.
Also as markdown: /stacks/activepieces.md
FAQ
- Why Redis?
- The official image uses Redis for the job queue. This template does not use in-memory Redis.
- n8n or Activepieces?
- Activepieces if you want Apache-2.0 and a simpler pieces model. n8n if you want the biggest node library — that template is /stacks/n8n-automation.