n8n Self-Hosting Alternative — Skip the VPS and Docker

The True Cost of Self-Hosted n8n

A minimal production n8n stack includes:

• A VPS — 2 vCPU / 4GB RAM minimum ($12–$24/month on Hetzner, DigitalOcean, or Linode)
• Managed Postgres or self-hosted Postgres with backups ($15+/month managed, or more memory on the VPS)
• Redis — required for queue mode ($5–$10/month managed)
• Domain + DNS hosting
• Let's Encrypt cert (free but needs automation)
• Reverse proxy config — nginx or Caddy
• Backup system — something to snapshot Postgres and the /data volume
• Monitoring — at minimum, uptime check + log aggregation

Realistic monthly infrastructure cost: $30–$60 once you include Postgres and backups. This is before you spend any time on updates or debugging.

The Operational Tax Nobody Mentions

Running n8n reliably means you also pay in hours:

• Updates: n8n ships fast. Every couple of weeks there is a security fix or breaking change. Updating means docker pull, migrations, and smoke-testing each active workflow.
• Postgres migrations: some n8n releases include schema migrations. If they fail, your workflows stop. Debugging Postgres migrations in Docker is not a fun Saturday.
• Disk fill: n8n stores every execution. A busy workflow can produce gigabytes per week. You need a scheduled purge job.
• Certificate renewal: Let's Encrypt certs renew every 90 days. If the renewal automation breaks, webhooks fail TLS and your senders get 5xx.
• Outages: VPS reboots, disk failures, upstream network issues. n8n goes down. Your Stripe webhooks pile up and get dropped after Stripe's retry window.

Two to six hours a month, every month, for as long as you run self-hosted n8n.

When Self-Hosting Is the Right Call

• You have a dedicated platform team with devops bandwidth
• You need data to stay on-prem for compliance (GDPR, HIPAA)
• You run 50+ workflows and have amortised the ops cost
• You need niche integrations that require a self-hosted deployment (local network APIs, private databases)
• You want to customise n8n's source

When a Hosted Alternative Wins

• You self-host n8n for fewer than 10 active workflows
• Your workflows are webhook-triggered (Stripe, Shopify, GitHub, etc.)
• You are the only person maintaining the n8n server
• You have been woken up at 3am because the webhook endpoint was down
• You are considering n8n Cloud because of the ops burden but do not want a per-execution bill

Requex.me: The Hosted Webhook Automation Layer

Requex.me is a hosted webhook automation platform. You sign in, create a webhook, and build a workflow on a visual canvas. There is no Docker, no VPS, no Postgres to manage.

What Requex covers that you would otherwise self-host n8n for:

• Receive webhooks on a stable public URL
• Verify HMAC signatures (Stripe, Shopify, GitHub presets)
• Deduplicate retries
• Transform payloads with JS or jq
• Branch, filter, and route to Slack, Discord, Email, HTTP, Google Sheets, Shopify
• Retry failing HTTP calls with exponential backoff
• Schedule workflows with cron expressions (including timezones)
• Inspect full run traces in a drawer

What Requex does not replace: deep OAuth-integrated data pipelines (Airtable as source, HubSpot CRM), 400+ app catalog, embedded scripting for complex ETL.

Cost Comparison (Illustrative)

Migration Path

Start with one workflow — not all of them. Pick the most-used or most-finicky n8n workflow, rebuild it on Requex using our migration guide, and run both in parallel for a week. If Requex handles it cleanly, migrate the rest one by one. The n8n box can be decommissioned once the last workflow is off.

FAQ