Skip to content
c17 .ioJoin list

Stacks / Automation

Easy

n8n or Activepieces + Postgres

Replace Zapier or Make with a self-hosted workflow engine and a real database.

The problem

Zapier and Make meter every run. A sales-ops or AI-agent shop hits four figures a month before the workflows are even interesting. You also cannot version, fork, or air-gap the graph.

Replaces

Zapier / Make

Estimated SaaS saved

$3,600

per year, small team, before lock-in

Deploy on Railway

Sponsor this stack

Placeholder: n8n or Activepieces + Postgres as a Railway template. Broad search demand; first automation template after the Go starter.

The stack

Cost table

You stop payingTypical / yearSelf-host instead
Zapier Professional (team)$3,600n8n + Postgres on Railway
Make Pro / Teams$2,400Activepieces + Postgres

Agent setup prompt

Deploy self-hosted automation that replaces Zapier.

Pick n8n (more nodes, fair-code) or Activepieces (fully open source). Pair it with Postgres.
- Persist uploads and SQLite/binary data on a volume if the app needs one; put structured data in Postgres.
- Set WEBHOOK_URL / PUBLIC_URL to the Railway public domain.
- Restrict the editor behind auth. Document how to import a "new subscriber → PocketBase → Resend" flow.
- Write AGENT_PROMPT.md and a cost table comparing Zapier task packs to this box.

Also as markdown: /stacks/n8n-automation.md

FAQ

n8n or Activepieces?
n8n if you want the biggest node library and don't mind fair-code licensing. Activepieces if you want Apache-2.0 and a simpler pieces model.
What about Make scenarios I already have?
Rebuild the top 5. Most Zapier/Make graphs are HTTP + a spreadsheet + Slack. Those are an afternoon in n8n.