What Is n8n Hosting? A Complete Guide
Where you host your automations shapes performance, security, and how much maintenance you must handle. You can self-host to keep the app and data under your control, or use managed n8n hosting like n8n Cloud to hand off infrastructure tasks and maintenance.
Your priorities determine the best setup. A solo creator automating a newsletter often prefers managed hosting for fast setup and low maintenance. An agency building client automations may host on a VPS to isolate client data and scale per account. E-commerce sites that process webhooks and sensitive orders commonly choose self-hosting or Cloud Run deployments to meet compliance and performance requirements while accepting extra operational work.
What you need to know
Before you pick a host, focus on a few practical essentials that affect reliability and cost. Hosting determines who is responsible for runtime, storage, backups, and scaling, and those decisions change your security posture and operating budget. The short list below highlights the items to check first.
- What it is: n8n hosting is where the runtime, workflows, and credentials live. It also defines who runs updates, handles scaling, and performs backups.
- Self-host vs Cloud: Self-hosting gives you direct control over data, privacy, and custom integrations but requires ongoing operations. Managed n8n Cloud removes most infrastructure work and provides faster setup with predictable billing.
- Preferred deployments: Docker Compose provides reproducible images and a simple update path for small teams. VPS, Kubernetes, and serverless options like Cloud Run fit different scale and operational comfort levels.
- Production essentials: Use PostgreSQL rather than SQLite, add Redis when using queue mode, and ensure persistent storage and SSL. Schedule regular backups and enable monitoring to protect workflows and data integrity.
- Action plan: Launch a small test instance and run one representative workflow to validate integrations and triggers.
You also like:
How to Choose the Best Web Hosting Provider
What is VPS Hosting: Complete Guide to Virtual Private Servers
What is Shared Hosting and How Does it Work? Pros And Cons
What is n8n hosting? Quick answer and who needs it
Quick answer: n8n hosting is the deployment and operation of the n8n workflow automation platform, either on your own infrastructure or through a managed SaaS. Hosting determines where the app runs, how workflows and credentials are stored, and who is responsible for updates, backups, and scaling. Users pick a hosting model based on the level of control they need, their budget, and technical comfort.
- Solo maker automating newsletters. Managed hosting is often the fastest route for a single creator because it minimizes setup and ongoing maintenance. Self-hosting on a small VPS is an alternative when you want full control over API keys and execution limits, but it requires handling setup and updates.
- Small agency building client automations. Agencies frequently choose managed hosting to reduce onboarding friction and provide clients with predictable uptime. If contracts require strict data separation or custom integrations, agencies commonly run n8n on a VPS or in isolated environments.
- E-commerce store handling webhooks and inventory sync. Stores with high webhook volume need predictable scaling and strong data controls. Self-hosting lets you tune resources and meet compliance requirements, while managed services simplify burst scaling and lower day-to-day operational risk.
Self-hosted vs managed (n8n Cloud): pros, cons, and data control
Start with where your data will live and who can access it. Self-hosting keeps storage, logs, and retention under your control, which helps meet compliance or client contract requirements. Managed hosting stores data with the vendor and removes much of the administrative work.
Operational responsibilities diverge. Self-hosting requires you to manage updates, security patches, backups, scaling, and monitoring; many teams run n8n in Docker on a VPS or cloud VM and add PostgreSQL and Redis for persistence. Managed n8n Cloud handles patching, backups, and scaling and typically includes features such as SSO and UI-managed backups; managed plans may impose execution limits while self-hosting removes those caps and allows custom nodes and private integrations.
Pick managed hosting when you want minimal day-to-day DevOps and faster time-to-value. Choose self-hosting when you need customization, data sovereignty, guaranteed throughput, or specialized compliance controls.
How to deploy n8n: Docker, VPS, Kubernetes, and Cloud Run
Docker Compose is a practical starting point for most teams because it provides reproducible images, simple health checks, and a predictable update path. Use the official n8n image, enable queue mode for horizontal workers when needed, and use named volumes for n8n data and your external database to preserve state across restarts. Updating is typically as simple as pulling a new image and restarting services, which makes Docker Compose attractive for many production setups.
Choose a VPS when you want full control without the overhead of orchestration. Providers such as DigitalOcean, Linode, Hetzner, and Vultr offer low-cost VMs with direct SSH access and fewer moving parts, although scaling and maintenance are manual. For a starter production box, plan for at least 2 vCPU, 2 GB RAM, and 25 GB SSD, and rely on external PostgreSQL and Redis for reliability. For more on common VPS sizing and minimum requirements, see the n8n VPS requirements.
Adopt Kubernetes only when you need high availability and automated scaling for many concurrent workflows or unpredictable spikes. Kubernetes adds operational complexity: you must manage ingress, autoscaling, persistent volumes, and secrets. Consider managed clusters like GKE, EKS, or AKS to reduce cluster operations and run n8n in queue mode with scaled workers and a robust external database.
Serverless platforms such as Cloud Run remove server maintenance and provide automatic scaling for bursty, stateless tasks. Watch for cold starts, execution time limits, and ephemeral filesystems, and pair Cloud Run with Cloud SQL and a managed Redis for persistence and long-running jobs. After deployment, compare operational costs and backup strategies for each option to find the best fit for your workload.
After you deploy, review production components like PostgreSQL, Redis, durable storage, and SSL; these elements are essential regardless of the platform you choose.
Production components and best practices (Postgres, Redis, storage, SSL)
Use PostgreSQL for production instead of SQLite. PostgreSQL handles concurrency and long-running workflows and provides ACID guarantees, while SQLite is suitable only for testing and will bottleneck under load. For small deployments, start with a Postgres instance around 2 vCPU, 2 GB RAM, and 25 GB SSD, and give each n8n instance its own database or a dedicated schema.
Use Redis for queues and worker coordination when running queue mode or scaling multiple workers. Redis improves parallel execution and helps prevent duplicate runs by acting as the broker between the API and workers. Prefer a managed Redis or a small dedicated instance, and monitor latency and memory to avoid evictions during peaks.
Store files, attachments, and credentials in durable object storage such as S3 or an S3-compatible service, and treat local disks as ephemeral. Schedule daily database dumps and back up files according to their change rate. Export workflows as JSON from the UI for an additional recovery copy to reduce single-point-of-failure risk and speed recovery.
Secure and monitor your deployment by enforcing SSL, enabling authentication or SSO, and restricting access by IP or VPN. Rotate credentials on a regular cadence and configure alerts for sustained CPU or memory over 80 percent, rising database connection counts, and repeated workflow failures. Regular restore testing and proactive monitoring should be standard operating procedures for production systems.
Pricing models: compare self-hosting, managed hosts, and n8n Cloud
Choosing n8n hosting is also a financial decision: control, convenience, and cost all play a part. For basic self-hosted VPS deployments expect roughly $2–$10 per month for a low-volume instance, though prices vary by provider and region. Factor in engineering time for setup, monitoring, and upgrades because those operational hours often exceed the sticker price over time.
Managed hosting targets teams that want to reduce ops work and gain support. Entry-level managed plans often start in the low single digits and can rise to $30+ per month for added backups, support, and staging environments. When comparing plans, check whether database hosting, automatic updates, and managed scaling are included or billed separately.
n8n Cloud uses a SaaS subscription model and typically starts around $20–$50 per month for small teams, with execution quotas at lower tiers and overage fees for higher usage. The convenience of vendor-managed routing, security, and backups comes with less raw control and potential per-execution costs as usage grows. If you consider serverless deployments such as Cloud Run, include expected monthly executions when sizing costs.
Also include hidden costs in a 12-month total cost of ownership: engineering hours for setup and maintenance, backups and disaster recovery, monitoring and incident response, SSO and enterprise features, and taxes or currency differences. Run a 12-month projection to see which model fits your budget and risk tolerance. For a general primer on what n8n is and how teams use it, see this practical overview from Scalahosting.
Migration checklist and free migration assistance from Hospedagens Pro
Before you move an existing instance, run a short inventory to avoid surprises and keep downtime minimal. Export workflows, list service credentials and webhook endpoints, snapshot the database if possible, note scheduled workflows and cron timings, and reduce DNS TTL ahead of cutover. Validate the full process on staging before you touch production.
- Export workflows and map credentials
- Snapshot your PostgreSQL or primary database
- Document webhook endpoints and scheduled jobs
- Lower DNS TTL before cutover
- Validate a staging deployment first
Follow this ordered plan for a low-downtime migration: provision the new host and create PostgreSQL and Redis instances, configure environment variables, import workflows, and restore the DB on staging. Run full staging tests for webhooks and scheduled jobs, pause inbound traffic for cutover, switch DNS, and monitor runs closely while keeping the old instance reachable for a quick rollback. Have a rollback plan that preserves the old host with DNS fallback and a verification checklist that includes sample workflow runs, webhook receipts, and scheduled job execution.
Common pitfalls include missing environment variables, webhooks that do not re-register, incorrect DNS TTLs, and secrets accidentally committed to repositories. If anything goes wrong, revert DNS and restore the last stable DB snapshot before troubleshooting. Hospedagens Pro helps new hosting clients with export and import of workflows, mapping environment variables, testing webhooks, and validating runs with a typical turnaround of a few business days.
Choose the right n8n hosting for your needs
n8n hosting is the choice of who runs and maintains the platform that executes your automations. Self-hosting fits teams that need customization, privacy, and predictable throughput at scale, while managed hosting is better for teams that want fast setup and low operational overhead. Let your priorities—control versus convenience—guide the decision.
