Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want to self-host n8n for my business and not lose my workflows

Short answer

n8n's documentation recommends Docker for most self-hosting, with a persistent data volume, and warns that self-hosting mistakes can lead to data loss, security issues and downtime. A safe setup has persistent storage, a database, a pinned version, backups that include the encryption key, HTTPS and an update routine.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I followed a tutorial and n8n runs, but I do not know if it is safe.
  • I am afraid an update or a server restart will delete my workflows.
  • I do not know where the credentials and data are stored.
  • Nobody on my team owns the n8n server.
  • I need webhooks to work from the internet.

Why does this happen?

  1. Self-hosting makes you responsible for your data and for keeping it running

    n8n's installation page says self-hosting requires technical knowledge and warns that mistakes can lead to data loss, security issues and downtime, and it recommends its cloud product for people without server management experience.

  2. Without a data volume, data lives inside the container

    The docs mount a named volume at the n8n data directory so data persists across restarts, and recommend keeping it even with PostgreSQL because it holds encryption keys and instance logs. A setup without it can lose everything when the container is recreated.

  3. The default database is not meant for scale

    By default n8n uses SQLite, and the docs give a separate variant that connects to PostgreSQL. Queue mode, used for heavy load, needs a shared database and does not support SQLite.

  4. Version and time zone settings matter

    The docs say the stable tag is for production and that a specific version can be pinned. They also separate the container time zone from the time zone used by schedule nodes, so a schedule can run at the wrong hour if only one is set.

  5. Updates need a plan

    n8n recommends regular updates, testing in a copy, reading the release notes between versions, and a backup that includes the database and the encryption key before updating.

What can I do about it today?

  1. Decide who owns itName one person responsible for the server, the n8n login and the backups.
  2. Write down where it runsHosting provider, the account it is under, and who has access. The account should be in your company's name.
  3. Save the encryption key nown8n uses an encryption key to protect saved credentials. Ask your developer where it is stored and keep a copy somewhere safe, apart from the server.
  4. Export your workflows as a first backupIn n8n you can download workflows as files. It is not a full backup, but it is a safe start.
  5. Do not expose a test setup to the internetThe docs describe a tunnel as for local development only and not safe in production. Do not use it for real business data.

When should I bring someone in?

  • Real customer data or payments will flow through n8n.
  • You have no backups, or have never restored one.
  • Workflows need to receive calls from the internet, which means HTTPS and a proxy.

How do I handle it?

  1. Choose the simplest sound setupA single server with containers, a persistent volume, PostgreSQL, a pinned version and HTTPS in front. Queue mode only if the load needs it.
  2. Put secrets and settings in one documented placeEncryption key, database login, public address and time zone are recorded in a handover note stored in your accounts.
  3. Back up and test a restoreDatabase, data folder and key are copied on a schedule to a separate location, and one restore is rehearsed on a spare machine.
  4. Set an update routineRelease notes are read, a copy is updated first, and production is updated with a backup taken just before.
  5. Hand it overYou receive the logins, the notes and a short list of what to check each month.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is self-hosting n8n right for me?

It can be, if someone owns the server. n8n's own documentation recommends its cloud product for people with no server management experience.

Where are my credentials stored?

In n8n's database, protected by the encryption key. Without that key, the saved credentials cannot be read, which is why the key goes into the backup.

How much server do I need?

It depends on the data your workflows handle. n8n's memory page shows that data size, not the number of workflows, is the main driver, so I size the server from your real use.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.