How to Self Host n8n for Free in 2026 (Step-by-Step Guide)

For workflows that need to run when your computer is turned off, Oracle Cloud Always Free offers another hosting option, subject to account eligibility and server availability. This guide covers both installation methods, including configuration, security, backups, and troubleshooting.

Is n8n Free to Self Host?

Yes, n8n Community Edition is free to self host without a recurring n8n software subscription. It includes the workflow editor, automation nodes, integrations, scheduled triggers, webhooks, and supported AI workflow functionality. You manage the installation yourself, including its infrastructure, application updates, security, and data storage.

Which Features Are Included in n8n Community Edition?

n8n Community Edition includes the core tools needed to create and execute automated workflows. It supports application integrations, conditional logic, API requests, scheduled tasks, webhooks, and compatible AI nodes. The self-hosted edition does not use the standard monthly execution quota associated with paid n8n Cloud plans.

• Visual workflow editor: Build automations by connecting nodes.
• Application integrations: Connect supported business applications and APIs.
• Schedule Trigger: Execute workflows at configured times.
• Webhook nodes: Receive HTTP requests from other systems.
• AI integrations: Connect compatible AI services and models.
• Local data storage: Store workflows, credentials, and execution history in your managed environment.

Free Community Edition registration can unlock selected additional features. Advanced organizational capabilities, including some enterprise authentication, governance, collaboration, and source control features, require eligible paid editions.

Can Businesses Use n8n Community Edition for Free?

Businesses can use n8n Community Edition for permitted internal automation under n8n’s Sustainable Use License. Automating internal operations is different from selling access to n8n as a hosted service. Offering the workflow editor to customers or embedding n8n in a commercial product may require a separate commercial agreement.

Organizations deciding between free self hosting and managed subscriptions can compare the available editions, execution allowances, and licensing differences in n8n Pricing 2026.

What Are the Best Free Ways to Host n8n?

Local Docker and Oracle Cloud Always Free are two practical approaches to free n8n hosting. Docker works well for learning, developing, and testing workflows on an existing computer. Oracle Cloud can support a remotely hosted instance that remains available independently of your personal device, provided its free resources remain accessible.

Local Docker is the simplest starting point if you already have a compatible computer. Oracle Cloud requires more technical setup because you must manage an Ubuntu server, network permissions, and HTTPS access.

What Do You Need Before Installing n8n?

To self host n8n using Docker, you need a compatible operating system, Docker Engine, Docker Compose v2, sufficient system resources, and storage for your workflows. An internet connection is required to download the container image and install dependencies. Windows users must also satisfy Docker Desktop’s virtualization requirements.

What Are the System Requirements for Self Hosted n8n?

n8n does not have one universal hardware requirement that covers every automation workload. A basic SQLite installation requires fewer resources than complex AI workflows or a deployment handling many concurrent executions. Docker Desktop and your chosen operating system also have their own resource requirements.

• Operating system: Supported Windows, macOS, or Linux installation.
• Container engine: Docker Desktop or Docker Engine.
• Container management: Docker Compose v2.
• Memory: Enough RAM for the operating system, Docker, and the intended workload.
• Storage: Space for container images, workflow data, execution history, and backups.
• Windows support: Hardware virtualization and a compatible WSL 2 installation.
• Network access: Internet access for installation and any external services used by workflows.

For more advanced deployments, n8n’s documented Docker Compose stack with its AI Assistant sandbox requires at least 4 GB of RAM and 2 virtual CPUs. That requirement applies to the larger sandbox setup, not as a universal minimum for the basic installation used below.

Do You Need a VPS or Domain Name to Run n8n?

No. A local Docker installation does not require a VPS, public IP address, or purchased domain. The n8n editor runs through localhost on your own computer. A public hostname and HTTPS configuration become relevant when external applications must contact your instance or when you need secure remote browser access.

How Do You Self Host n8n for Free Using Docker?

Install Docker, create a persistent volume, prepare a Docker Compose configuration, and start the n8n service. This method uses the official n8n container image with SQLite as its default database. It provides a practical environment for learning, developing workflows, and testing supported integrations without paying for n8n Cloud hosting.

Step 1: How Do You Install Docker?

Install Docker Desktop on a supported Windows or macOS computer, or use Docker Engine with the Compose plugin on Linux. The installation must finish successfully before n8n can run. Windows users should confirm that hardware virtualization and the required WSL 2 components are enabled.

On Windows, open PowerShell as an administrator if WSL is missing and run:

wsl --install

Restart Windows if prompted. After opening Docker Desktop and starting its engine, verify the Docker installation from your terminal.

docker --version
docker compose version

Both commands should display version information. Linux users should perform these checks after installing Docker Engine and its Compose plugin.

Step 2: How Do You Create Persistent Storage?

Create a Docker volume so n8n can retain important data when its application container is replaced. The default SQLite database and instance configuration are stored in the n8n data directory. A named volume separates this storage from the container’s temporary filesystem.

Open your terminal and run:

docker volume create n8n_data

Docker should return n8n_data after successfully creating the volume.

The Compose configuration will mount this volume at /home/node/.n8n. Keep the volume name consistent throughout the setup.

Step 3: How Do You Configure Docker Compose for n8n?

Create a project folder containing a compose.yaml file. Docker Compose uses this file to define the n8n container, its environment variables, the local network port, and persistent storage. The configuration below binds the editor to your computer instead of exposing it directly to the public internet.

Create a folder named n8n-compose and save the following content in compose.yaml:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    container_name: n8n
    restart: unless-stopped
    ports:
      - "127.0.0.1:5678:5678"
    environment:
      TZ: Etc/UTC
      GENERIC_TIMEZONE: Etc/UTC
      N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS: "true"
    volumes:
      - n8n_data:/home/node/.n8n

volumes:
  n8n_data:
    external: true

Replace Etc/UTC with an appropriate IANA timezone if your scheduled workflows must follow local time.

For a production environment, choose and pin a tested n8n image version rather than relying indefinitely on an automatically changing image tag.

Open a terminal in the folder containing your Compose file and validate it:

docker compose config

A valid configuration should be displayed without Compose validation errors.

Step 4: How Do You Start the n8n Container?

Start n8n by running Docker Compose from your project directory. Docker downloads the required image if it is not already available, creates the container, and starts the application in the background. Initial startup may take longer while Docker downloads the image layers.

docker compose up -d

Check the container status:

docker compose ps

The n8n service should appear with a running status.

Step 5: How Do You Open n8n and Create Your Account?

Open http://localhost:5678 in your browser after Docker reports that the container is running. The initial setup page allows you to create the instance owner account. Once you complete registration and sign in, n8n displays the workflow editor.

Create your owner account using an email address and a strong password. Keep these credentials secure because the account controls your local automation environment.

n8n may also offer free Community Edition registration for selected additional features. This registration is separate from a paid Cloud subscription.

Step 6: How Do You Create and Test Your First n8n Workflow?

Create a workflow with a Manual Trigger and an Edit Fields node to verify that n8n can execute automation steps correctly. This test requires no external service credentials and confirms that the workflow editor can process data and display execution results.

1. Open the n8n dashboard and create a new workflow.
2. Add a Manual Trigger node.
3. Connect an Edit Fields node to the trigger.
4. Create a field named message.
5. Set its value to Hello from my self hosted n8n.
6. Select Execute Workflow.
7. Confirm that the output contains the message.

Once this test succeeds, you can explore integrations with applications such as Notion, Google Sheets, and email services.

For example, n8n can send form submissions to a Notion database or update project records. If your workflow also depends on premium Notion workspace features, compare the available Notion AI subscription options on Primingo. A paid Notion AI plan is not required for every basic Notion integration.

Step 7: How Do You Check That n8n Saves Your Workflows?

Restart the n8n container after saving your test workflow, then confirm that the workflow remains available. This verifies that the instance can retrieve its existing database after a normal restart. It is a useful installation check before creating more complicated automations.

Run the following command from the Compose project folder:

docker compose restart

Open the editor again and confirm that your saved workflow is present.

You can also test normal container recreation:

docker compose down
docker compose up -d

This setup uses an external named volume, so removing the application container does not remove that volume. Do not delete n8n_data unless you intentionally want to remove the stored instance data.

How Can You Host n8n for Free 24/7 Using Oracle Cloud?

You can run n8n on an eligible Oracle Cloud Always Free virtual machine by creating an Ubuntu server, installing Docker, and configuring secure remote access. The server operates independently of your personal computer. However, Oracle Cloud does not guarantee permanent resource availability or uninterrupted uptime for Always Free instances.

Step 1: How Do You Create an Oracle Cloud Free Tier Account?

Register for Oracle Cloud Free Tier and complete the required account verification. Oracle generally requires an accepted payment card and identity information during registration. Select your home region carefully because Always Free compute resources must be created in that region.

Oracle distinguishes Always Free resources from temporary trial credits. Confirm that the resources selected during setup carry the appropriate Always Free eligibility before provisioning them.

Step 2: How Do You Create an Always Free Ubuntu VM?

Create an Ubuntu virtual machine using an eligible Oracle Cloud compute shape. According to Oracle’s Always Free resource documentation updated June 12, 2026, eligible Ampere A1 compute usage includes 1,500 OCPU hours and 9,000 GB hours of memory per month, equivalent to 2 OCPUs and 12 GB of memory for an Always Free tenancy.

Follow these steps in the Oracle Cloud Console:

1. Open Compute and select Instances.
2. Choose the option to create an instance.
3. Select an eligible Ubuntu image.
4. Choose an Always Free eligible compute shape such as VM.Standard.A1.Flex.
5. Allocate CPU and memory resources within your available free allowance.
6. Configure the virtual cloud network and subnet.
7. Assign a suitable public IP address for remote administration.
8. Generate or upload an SSH public key.
9. Review the configuration and create the instance.

Oracle also offers eligible AMD micro instances, although their resource specifications differ from Ampere A1 shapes.

Some regions temporarily lack capacity for particular free compute shapes. Oracle may also reclaim qualifying idle Always Free instances. These limitations make free cloud hosting less predictable than infrastructure with contractual availability commitments.

Step 3: How Do You Install Docker on Oracle Cloud Ubuntu?

Connect to the Ubuntu VM through SSH and install Docker Engine using Docker’s official package repository. The repository installation method supports future package updates and provides the Docker Compose plugin required for this tutorial. Use commands compatible with the Ubuntu version installed on your server.

Connect using your private SSH key:

ssh -i your-private-key ubuntu@YOUR_SERVER_IP

Replace the example key filename and server address with your actual values.

Update Ubuntu and install the packages required to configure Docker’s repository:

sudo apt update
sudo apt install -y ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings

Download Docker’s official repository signing key:

sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

Create the Docker repository configuration:

sudo tee /etc/apt/sources.list.d/docker.sources >/dev/null <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF

Install Docker Engine and the Compose plugin:

sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Verify that Docker is available:

sudo docker --version
sudo docker compose version

These commands follow Docker’s documented Ubuntu repository installation method. For supported Ubuntu releases, package conflicts, and future changes, consult the official Docker Engine installation guide for Ubuntu.

Step 4: How Do You Deploy n8n on Your Oracle Cloud Server?

Deploy n8n on the Ubuntu VM using the same persistent storage and Compose structure as the local installation. For public hosting, add environment variables describing your external hostname and reverse proxy. Keep the application bound to localhost so Nginx can handle incoming HTTPS connections.

Create the project directory and volume:

mkdir -p ~/n8n-compose
cd ~/n8n-compose
sudo docker volume create n8n_data

Create compose.yaml:

nano compose.yaml

Copy the Compose configuration from the local Docker section into this file. Under the existing environment settings, add the following entries:

N8N_HOST: n8n.example.com
N8N_PROTOCOL: https
N8N_EDITOR_BASE_URL: https://n8n.example.com/
N8N_WEBHOOK_URL: https://n8n.example.com/
N8N_PROXY_HOPS: "1"

Replace n8n.example.com with the hostname you control. Indent these entries to match the existing environment variables in the YAML file.

n8n’s current reverse proxy documentation uses N8N_WEBHOOK_URL for the public webhook address. The former WEBHOOK_URL setting became deprecated in n8n 2.35.0.

Save the Compose file, validate its structure, and start the container:

sudo docker compose config
sudo docker compose up -d
sudo docker compose ps

The application is now running on Ubuntu, but its public HTTPS endpoint still requires configuration.

Step 5: How Do You Configure Nginx and HTTPS for n8n?

Configure Nginx as a reverse proxy and obtain a TLS certificate for the hostname assigned to your n8n server. HTTPS protects browser connections and supports integrations requiring secure callback URLs. Your DNS record must point to the server before certificate validation can succeed.

Create a DNS A record that resolves your chosen hostname to the VM’s public IPv4 address.

In Oracle Cloud networking, allow inbound TCP traffic on ports 80 and 443. Restrict SSH access on port 22 to trusted addresses whenever possible. Any enabled operating system firewall must also permit the required traffic.

Install Nginx and Certbot:

sudo apt install -y nginx certbot python3-certbot-nginx

Create an Nginx site configuration:

sudo nano /etc/nginx/sites-available/n8n

Paste the following configuration and replace the hostname:

server {
    listen 80;
    server_name n8n.example.com;

    location / {
        proxy_pass http://127.0.0.1:5678;
        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Enable the site and validate Nginx:

sudo ln -s /etc/nginx/sites-available/n8n /etc/nginx/sites-enabled/n8n
sudo nginx -t
sudo systemctl reload nginx

If another Nginx configuration already handles the hostname or port, resolve that conflict before reloading the service.

Request a certificate using Certbot:

sudo certbot --nginx -d n8n.example.com

Follow the certificate prompts and enable an HTTP to HTTPS redirect when appropriate.

Never expose port 5678 publicly simply to bypass the reverse proxy. The Docker port binding already limits direct application access to localhost on the server.

Step 6: How Do You Verify That n8n Runs Independently?

Test remote hosting by opening the HTTPS dashboard, creating a scheduled workflow, and checking whether it executes after you disconnect from the server. This confirms that the automation runs inside the cloud instance rather than depending on an open browser or an active SSH session.

1. Open your configured HTTPS hostname.
2. Complete the n8n owner account setup.
3. Create a workflow using Schedule Trigger.
4. Connect an Edit Fields node that outputs a test message.
5. Configure a suitable schedule and test the workflow.
6. Save and publish the workflow to enable production scheduling.
7. Close your browser and disconnect from SSH.
8. After the scheduled execution time, reconnect and inspect execution history.

Current n8n versions use workflow publishing to enable production triggers. A saved draft alone does not necessarily activate a scheduled workflow.

How Do You Secure, Back Up, and Update Self Hosted n8n?

Secure n8n by protecting account credentials, restricting server access, using HTTPS, and maintaining independent backups. Application data should survive normal container replacement, but persistent storage alone cannot recover information lost through disk failure, accidental volume deletion, or the permanent loss of a cloud server.

How Should You Secure Your n8n Instance?

Protect the n8n owner account and limit access to the server and its stored credentials. For remote installations, use HTTPS and restrict administrative ports. Treat third-party community nodes, workflow credentials, and downloaded extensions as potential security risks because they can interact with connected services and sensitive information.

• Use a strong, unique owner account password.
• Enable available multifactor authentication where supported.
• Keep Docker, Ubuntu, and n8n updated.
• Limit SSH access to trusted addresses.
• Do not publish API keys or encryption secrets in public repositories.
• Restrict access to configuration files and backups.
• Protect sensitive webhooks using supported authentication methods.
• Review community nodes before installation.

For business systems, also review workflow permissions and the credentials used to connect external applications. Use dedicated service accounts where appropriate.

How Do You Back Up n8n Docker Data?

Back up the persistent Docker volume containing the instance database and encryption information. For a SQLite installation, stopping n8n before creating a volume archive helps prevent database changes during the backup. Store the completed archive separately from the machine hosting the application.

The following commands use a Bash-compatible shell on Linux or macOS. Windows users can adapt the host directory mount for their Docker environment.

Stop the application from its Compose project directory:

docker compose stop

Create the archive:

docker run --rm \
  -v n8n_data:/data:ro \
  -v "$PWD":/backup \
  alpine \
  tar -czf /backup/n8n-backup.tar.gz -C /data .

Restart n8n:

docker compose start

For an Ubuntu server where Docker requires administrator privileges, prefix the applicable Docker commands with sudo.

The resulting n8n-backup.tar.gz archive may contain confidential application data. Protect it with appropriate storage permissions and encryption.

How Do You Restore n8n From a Backup?

Restore a Docker volume archive into a new named volume before attempting recovery of the original installation. Testing the backup separately reduces the risk of overwriting working data. A successful recovery should confirm that workflows, user access, and encrypted credentials function as expected.

Create a separate recovery volume:

docker volume create n8n_restored

Place your backup archive in the current directory and extract it:

docker run --rm \
  -v n8n_restored:/data \
  -v "$PWD":/backup:ro \
  alpine \
  sh -c 'cd /data && tar -xzf /backup/n8n-backup.tar.gz'

To test the restored data, create a separate Compose project that uses n8n_restored instead of n8n_data. Assign a different container name and bind its application port to 127.0.0.1:5679.

Use a compatible n8n version, preserve the original encryption key, and verify the recovered workflows. Prevent the test instance from running live business automations unintentionally.

How Do You Update n8n Without Losing Workflows?

Update n8n by reviewing the relevant release notes, creating a verified backup, downloading the approved container image, and recreating the application container. Docker Compose keeps the existing external data volume attached when the service is recreated with the same volume configuration.

From your Compose project folder, run:

docker compose pull
docker compose up -d

Test important workflows after the update. For production systems, review breaking changes and use explicit image versions so upgrades can be planned and tested rather than applied unexpectedly.

How Much Does Self Hosted n8n Actually Cost?

n8n Community Edition has no recurring n8n software fee, but the total cost of self hosting depends on infrastructure and connected services. Running n8n on an existing computer avoids a separate server subscription, while eligible Oracle Cloud resources can reduce cloud hosting charges. Electricity, storage, domains, backups, and external APIs may still create expenses.

When Do n8n Integrations Create Extra Costs?

External services can charge for API calls, email delivery, AI model usage, or premium workspace features even when n8n itself is free. The cost depends on the service and the volume of activity processed by your workflows. Evaluate the connected application’s limits before activating automation that runs frequently.

For example, an n8n workflow that sends order confirmations through Resend may consume email sending allowances. Businesses planning this integration can review Resend Pricing 2026 to understand the provider’s separate billing model.

Workflows that update Notion databases generally use Notion’s supported integration capabilities. If the same process relies on Notion AI features, their availability and potential credit charges are separate concerns. The article Notion AI Pricing explains those workspace and AI usage differences.

When Is a Paid n8n Subscription Worth Considering?

A managed subscription becomes relevant when you prefer provider-managed hosting instead of administering Docker, operating system updates, remote access, and server availability. Compare the workload’s execution requirements, security needs, account ownership, and support arrangements before choosing a paid option.

If you decide that managed access fits your requirements, you can grab your n8n subscription on Primingo. This is a separate marketplace offer, so verify its activation method, execution allowance, access terms, and renewal conditions. It is not necessary for the free installation explained here.

How Do You Fix Common n8n Self Hosting Problems?

Most initial n8n hosting problems involve Docker startup errors, incorrect port bindings, storage configuration, webhook accessibility, or server permissions. Start by checking the application status and container logs, then compare the error against the relevant configuration. Avoid deleting containers or volumes before identifying where the original data is stored.

Why Is the n8n Docker Container Not Starting?

An n8n Docker container may fail to start because of invalid Compose settings, unavailable system resources, file permission problems, or an application startup error. The container logs provide the most useful starting point because they identify what happened during initialization.

Run these commands from the project directory:

docker compose ps
docker compose logs --tail=100 n8n

Correct the specific reported error before restarting the application. Use sudo on Linux if Docker permissions require it.

Why Is localhost:5678 Not Opening n8n?

The local n8n dashboard may not open if Docker is stopped, the container failed to start, or another application occupies port 5678. First confirm that Docker is running. Then check the service’s port mapping and whether the browser is accessing the same computer hosting n8n.

If port 5678 is already in use, identify the conflicting application before changing the Compose configuration.

Why Is Your n8n Webhook Not Triggering?

An n8n webhook may fail when the external sender cannot reach the public endpoint, the workflow is not published, or the reverse proxy forwards requests incorrectly. Test webhooks and production webhooks have different behavior, so verify that the URL belongs to the intended execution mode.

1. Confirm that the production workflow is published.
2. Verify the external HTTPS hostname.
3. Check that the reverse proxy forwards incoming requests.
4. Ensure the relevant firewall rules permit traffic.
5. Confirm the configured public webhook URL.
6. Inspect execution history and application logs.

A local installation bound to localhost can receive requests from the hosting computer, but external applications cannot reach that address directly. Public integrations require an appropriately configured public endpoint or development tunnel.

Why Do n8n Workflows Disappear After Restarting?

Workflows may appear missing when the recreated container uses a different Docker volume or database from the original installation. Inspect the active container mounts before making further configuration changes. The workflow data may still exist in a previously created volume.

List the available volumes:

docker volume ls

Inspect the container mounts:

docker inspect n8n --format '{{json .Mounts}}'

For the installation in this guide, confirm that the expected volume is mounted at /home/node/.n8n.

Do not remove unidentified volumes until you have confirmed which one contains the original instance data.

Which Free n8n Hosting Option Should You Start With?

Start with local Docker if your priority is learning n8n or testing workflows without paying for a server. Choose eligible Oracle Cloud hosting when scheduled automation needs an independent remote environment and you are prepared to manage Linux, networking, and backups. For critical operations, evaluate reliability and recovery requirements before depending on free resources.

Once your automation is working, you can explore other relevant workflow and productivity products through Primingo. Keep the free n8n installation separate from any optional paid software used by connected applications.

Frequently Asked Questions About Free n8n Self Hosting

Can I Self Host n8n for Free Without a Credit Card?

Yes. You can install n8n Community Edition locally using Docker without providing a credit card to n8n. Docker Desktop is free for eligible users under its licensing terms. Oracle Cloud generally requires an accepted payment card during account verification, even when you intend to use only Always Free resources.

Can I Install n8n Without Docker?

Yes. n8n supports installation through npm on a compatible Node.js environment. Docker is not mandatory, but it offers an isolated application environment and makes container recreation easier to manage. Choose npm when you understand the required Node.js version, dependency management, application storage, and process supervision.

Can I Move My Local n8n Installation to a Cloud Server?

Yes. You can migrate n8n from a local computer to a cloud server by transferring compatible application data, database contents, and configuration. Preserve the original encryption key so saved credentials remain usable. Test the restored instance before directing production workflows to the new server.

Does Self Hosted n8n Need a GPU?

No. Standard n8n workflows do not require a GPU. The application can run on a compatible CPU-based server. A GPU may become useful when you separately host demanding AI models or other computational workloads. Connecting n8n to a remote AI provider does not require your n8n server to perform the model’s computation.

Can n8n Work Without an Internet Connection?

Yes, locally hosted n8n can execute workflows that depend only on available local resources, provided the application and required components are already installed. Workflows that connect to cloud APIs, external AI providers, email services, or other internet-based systems need network access to those destinations. Installation and software updates also require access to the relevant download sources.