Last month I audited my own subscription stack and found three automation tools I was paying for monthly, each doing one small job: one watched an RSS feed, one moved form submissions into a spreadsheet, one posted to social media. Total cost: more than my VPS. Total complexity: three dashboards, three logins, three privacy policies holding my data.
So I did what any self-hoster would do: deleted all three and ran one container. The replacement is n8n — a workflow automation tool you self-host, connect to ~400 services, and keep entirely on your own infrastructure. It's the closest thing to "Zapier, but mine" that I've found, and this post is the honest setup guide — including the license asterisk you should read before falling in love.
First, the asterisk: it's not open source
Full disclosure, because this blog cares about that stuff (see what happened when HashiCorp changed Vault's license): n8n uses a "fair-code" license (Sustainable Use License). Source-available, free to self-host and use, but with commercial restrictions and not OSI-approved. My read: for personal automation it's a non-issue; if you're building a product on top of it, read the license or reach for something like Windmill or Activepieces instead. Know what you're adopting — that goes for every tool on this blog.
The honest setup
One docker-compose file, following the same pattern as the rest of my stack — app container, real database (not SQLite, you'll thank me at 10,000 executions), one reverse proxy in front:
services: n8n: image: docker.n8n.io/n8nio/n8n:latest restart: unless-stopped environment: - N8N_HOST=n8n.mydomain.com - N8N_PROTOCOL=https - WEBHOOK_URL=https://n8n.mydomain.com/ - DB_TYPE=postgresdb - DB_POSTGRESDB_HOST=postgres - DB_POSTGRESDB_USER=n8n - DB_POSTGRESDB_PASSWORD=${DB_PASSWORD} - N8N_ENCRYPTION_KEY=${ENCRYPTION_KEY} volumes: - n8n-data:/home/node/.n8n depends_on: - postgres postgres: image: postgres:17-alpine restart: unless-stopped environment: - POSTGRES_USER=n8n - POSTGRES_PASSWORD=${DB_PASSWORD} - POSTGRES_DB=n8n volumes: - pg-data:/var/lib/postgresql/data volumes: n8n-data: pg-data: Two environment variables deserve your attention before docker compose up:
-
N8N_ENCRYPTION_KEY— set it once, generate a long random string, and never lose it. It encrypts stored credentials. Losing it means re-entering every API key in every workflow; I keep mine in the password manager next to the OpenBao unseal keys. -
WEBHOOK_URL— must be your public HTTPS URL, or your webhook triggers will generate broken URLs silently and you'll debug it for an embarrassing length of time. Ask me how I know.
Then point your DNS at the box, put nginx in front with a real certificate — the same dance as everything else on this domain, covered in the reverse proxy guide — and open the URL. First run creates your owner account.
Webhooks are the point — protect them
The power move with n8n is the webhook trigger: an HTTP endpoint that starts a workflow. That's also your attack surface. Two rules:
- Authentication on by default. n8n webhook nodes support header or basic auth — enable it for anything that touches private data. An unauthenticated webhook that posts to your social accounts is a remote-control you left on the porch.
- Keep it off the open internet where you can. My instance sits behind the same VPN-plus-proxy arrangement as my other admin tools; the Tailscale setup gets used here too. If a workflow must be public (like a form), that's the exception, and it gets its own auth and rate limits.
What I actually automated (the three-subscription replacement)
The original three jobs, rebuilt as two workflows:
1. RSS → filtered digest. Trigger node polls a few feeds hourly, a filter drops everything that doesn't match keywords I'm tracking, and the survivors land in a Telegram message each morning. Replaces the RSS-watcher subscription — and the keyword filter is better because I wrote it.
2. Form → spreadsheet → draft social post. A webhook receives a form submission, n8n appends a row to a Google Sheet (the integrations are first-class — OAuth setup takes minutes), then drafts a social post I review before anything goes live. Human in the loop, automation doing the boring 90%.
Total running time per execution: seconds. Total cost: the VPS I was already paying for. There's also an AI node if you want to wire in a local model through the Ollama setup — summarize-then-post is where I'm experimenting next.
Where self-hosted n8n wins — and where it doesn't
Wins, honestly:
- Execution-based pricing beats per-step pricing at volume. On Zapier, a ten-step workflow burns ten tasks; on Make, every module burns credits. Self-hosted n8n doesn't meter you at all — my digest workflow would be a metered horror on the hosted tiers.
- Your data stays home. Form submissions and API keys live on your disk, not in someone else's multi-tenant database. For a privacy-first stack, that's the whole argument.
- Code when you want it. Every node can fall through to a JavaScript or Python step. Some of my "workflows" are 80% code nodes, and that's fine — the visual layer documents itself.
Losses, equally honest:
- You own the uptime. When the 7 AM digest doesn't arrive, that's your container to debug, not a status page to check.
- No support contract. The community forum is genuinely good; a Slack channel with an SLA it is not.
- Complex branching logic gets messy in a visual editor faster than you'd think. Past a certain complexity, it's a real application — write it as one.
Backup, because I always say it
Your workflows and credentials live in Postgres now, which means your existing Postgres backup routine covers everything. Take the volume backup too (n8n-data holds the encryption key material — back it up, or your credential backups are unreadable). Test a restore once; an automation tool whose config you can't restore is a very elaborate way to lose your afternoons.
Worth it?
If you pay for one or two lightweight automation subscriptions and already run a server: yes, emphatically. An afternoon of setup traded for permanently lower bills and a stack that keeps your data home is exactly the trade this blog exists to make. Just go in with open eyes about the license, set the encryption key before the first credential, and put auth on every webhook.
And if you build the AI-summary workflow before I do — the RSS digest summarized by a local model every morning — tell me how it goes. That's the next post brewing.
