n8n Hosting with Automated Backups — Never Lose a Workflow

Our backup process captures everything n8n needs to function: the PostgreSQL database containing all workflows, credentials (encrypted), execution history, webhook registrations, and n8n settings. We also back up n8n's environment configuration, Nginx configuration, SSL certificates, and any custom files you've added to the server.

The backup is comprehensive enough to rebuild your entire n8n instance from scratch on a new server. If your current server suffers catastrophic hardware failure, we restore your backup to replacement hardware and your n8n instance comes back online with every workflow, every credential, and every configuration setting intact.

Binary data from workflow executions (file attachments, images, documents processed by workflows) is included if stored locally. If you configure n8n to use external storage (S3-compatible), the external storage is backed up separately based on your storage provider's backup policies.

Full backups run daily during your server's lowest-traffic window (configurable, default 3:00 AM server time). The backup process uses pg_dump with custom format for efficient compression and selective restoration. A typical n8n database with thousands of workflow executions compresses to a fraction of its on-disk size.

We retain 14 daily backups by default, giving you a two-week recovery window. For businesses that need longer retention, we offer 30-day and 90-day retention plans. Extended retention is especially useful if you need to recover from a data corruption issue that isn't noticed immediately.

Backups are stored on physically separate storage from your server's primary drives. A single-disk failure, RAID controller issue, or filesystem corruption on the primary storage doesn't affect your backup data. For maximum protection, we offer geo-redundant backup storage with copies in a different data center.

Daily backups cover most recovery scenarios, but what about data loss that happens between backups? Our PostgreSQL WAL (Write-Ahead Log) archiving enables point-in-time recovery — the ability to restore your database to any specific second in time, not just the last daily backup.

If you accidentally delete a critical workflow at 2:15 PM and the last backup ran at 3:00 AM, traditional backups would lose 11 hours of changes. With WAL-based point-in-time recovery, we restore to 2:14 PM — recovering everything except the deleted workflow, which we can then restore individually from the backup without affecting recent changes.

Need a backup right now? You can trigger an on-demand backup at any time through our support channel. This is recommended before making significant changes to your n8n instance — upgrading n8n versions, modifying complex workflows, or changing credential configurations. The on-demand backup runs immediately and doesn't affect your regular backup schedule.

We also provide downloadable backup files on request. If you want to maintain your own off-site backup copies, test your workflows in a local development environment, or prepare for a server migration, we'll provide a compressed backup file you can download and store wherever you choose.

For managed hosting customers, we handle all backup-related requests — restoration, on-demand snapshots, retention changes, and backup verification. For unmanaged hosting, we provide documentation and scripts for setting up your own backup process, with our team available to assist if needed.