For a new self-hosted n8n instance, use the official one-line Docker Compose setup: curl -fsSL https://get.n8n.io | sh. It creates a ready-to-run stack and serves n8n at http://localhost:5678. Choose hand-written Docker Compose when you need to change the stack, database, networking or security model. Choose n8n Cloud when you want n8n to operate the infrastructure. Standalone Docker is now an outdated, mainly local-development path, and npm is primarily for existing installations because new n8n 3.0 installations are distributed through Docker.
Which n8n installation method should you use?
The right method depends on who owns the infrastructure and how much control you need. A quick fresh self-hosted installation is easiest with the one-line setup. A production deployment that must fit an existing Compose project is better built by hand. If you do not want to maintain servers, networking, upgrades, databases, backups and security controls, n8n Cloud removes that operational work. Cloud-provider deployments preserve control of your own account but leave every infrastructure task with you.
As an Amazon Associate I earn from qualifying purchases.
- Fastest new self-hosted start: official one-line Docker Compose setup.
- Maximum configuration control: hand-built Docker Compose.
- Local testing of an existing container workflow: standalone Docker, with the warning that its official page is outdated.
- Existing legacy installation: keep the npm installation working, but consult current documentation before any upgrade.
- Your own cloud account and architecture: deploy through a documented cloud-provider route.
- No infrastructure maintenance: n8n Cloud.
n8n installation methods compared
| Method | Best fit | Main prerequisites | Operational burden | Key caveat |
|---|---|---|---|---|
| One-line setup | Fast fresh self-hosted start | Docker and Compose v2 | Low to moderate | Intended for new installs; generated stack uses SQLite by default |
| Docker Compose by hand | Configuration control, existing Compose projects, production customization | Docker Engine, Compose v2, 4 GB RAM and 2 vCPUs for the bundled sandbox | Moderate to high | Secrets, volumes, database and sandbox need deliberate configuration |
| Standalone Docker | Local development and testing | Docker Desktop or Docker Engine | Moderate | Official page is marked outdated and points to Compose |
| npm | Existing installations or legacy workflows | Check current Node and npm requirements in the official documentation | Variable | New n8n 3.0 installations and future upgrades should use Docker |
| Cloud provider | Operators wanting their own cloud account and infrastructure control | Provider account, networking, TLS and database plan | High | Provider guides differ and you own operations |
| n8n Cloud | Managed hosting | Account and plan selection | Low | 14-day trial, 1,000 executions and workspace deletion after expiry unless upgraded |
What to decide before installing
Self-hosting versus managed hosting
Self-hosting means you are responsible for the host, container runtime, storage, network exposure, TLS, database, backups, monitoring, upgrades and incident recovery. n8n’s own prerequisite guidance describes the required knowledge as setting up and configuring servers and containers, managing resources and scaling, securing servers and applications, and configuring n8n. If those responsibilities are outside your team’s experience or available time, managed hosting is the safer operational choice.
SQLite versus PostgreSQL
The quick setup and the example Compose stack use SQLite by default. SQLite is convenient for trying n8n or running a small personal instance. The Compose guidance recommends PostgreSQL for teams and production environments, especially when more than a handful of users or continuously running workflows are involved. Treat the database decision as part of the initial design: the fresh-instance example does not automatically migrate existing SQLite data to PostgreSQL.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Local access versus public access
The one-line setup is immediately reachable at http://localhost:5678, which is suitable for a machine you control locally. A public deployment needs a deliberate hostname, TLS termination, firewall policy, authentication and backup plan. Do not expose the bundled sandbox services to the public internet.
Method 1: install n8n with the official one-line setup
This is the recommended starting point for a new self-hosted installation. It uses Docker Compose v2 and generates the files and services needed for a working instance.
Prerequisites
- Docker must already be installed and running.
- The Docker Compose v2 plugin must be available. The older standalone
docker-composebinary is not the prerequisite for this guide. - You need permission to run Docker and write the installation directory.
Run the installer
- Open a shell on the machine where n8n should run.
- Run the official command exactly as shown:
curl -fsSL https://get.n8n.io | sh. - Let the script create an
n8ndirectory, writecompose.yml,.envand related configuration, download images and start the services. - Open the local address reported by the script, normally
http://localhost:5678.
The generated setup stores its project files in the directory and workflow data in an n8n-data Docker volume. The stack includes n8n, SQLite and optional Assistant support services. That combination is convenient for evaluation and small installations, but a busy team should plan a PostgreSQL-backed design instead of treating the default SQLite choice as a production recommendation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsStop, start and upgrade
From the directory containing the generated files, stop the stack with docker compose -f ./n8n/compose.yml down. Start it again in the background with docker compose -f ./n8n/compose.yml up -d. To apply the installer’s upgrade flow, run curl -fsSL https://get.n8n.io | sh -s -- --upgrade.
Be careful with removal commands. Bringing the stack down with volumes, such as docker compose -f ./n8n/compose.yml down -v, deletes the n8n data volume. Use that only when you intentionally want to erase the instance, and make a verified backup before destructive maintenance.
When the one-line setup is the wrong choice
Use another method if you must merge n8n into an existing Compose project, replace SQLite immediately, change the bundled services, enforce a custom network layout or implement a production topology that the generated files do not express. In those cases, the script is a useful starting point, not a substitute for designing the stack.
Method 2: build a Docker Compose deployment by hand
Hand-built Compose is the control-oriented option. It is appropriate when you need to inspect and edit every service, integrate n8n with an existing Compose project or prepare a deployment for a team.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Resource and runtime requirements
- Docker Engine.
- Docker Compose v2.
- At least 4 GB of RAM and 2 vCPUs for the documented sandbox stack.
Those resources apply to the stack described in the guide, which includes more than the n8n application itself. Size the host for your workflow concurrency, execution history, database, queueing design and any adjacent services rather than assuming the minimum is a universal production size.
What the documented stack contains
The example includes n8n, sandbox certificate generation, a sandbox API, a privileged sandbox runner and SearXNG. Each component has a role in the example environment, so removing or exposing one changes the security and functionality assumptions. Keep sandbox containers on an internal network and expose only the n8n service through the cloud firewall or host firewall.
Start and verify the stack
- Prepare the Compose file and environment values, replacing every placeholder secret with a unique value.
- Start the services with
docker compose up -d. - Inspect service state with
docker compose ps. - Check the n8n health endpoint with
curl -sf http://localhost:5678/healthz.
A successful health check confirms that the n8n HTTP service responds; it does not prove that backups, external credentials, database durability, TLS or every sandbox function is correctly configured. Test those separately before inviting users to build critical workflows.
Choose the database deliberately
SQLite is included by default in the example. For a production instance serving more than a handful of users or running workflows continuously, use PostgreSQL instead. The guide’s fresh-instance example does not migrate SQLite data automatically, so decide whether you are starting clean or performing a separate, planned migration. Keep database credentials outside the Compose file where practical, restrict database network access and include the database in backup and restore tests.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Security controls that cannot be optional
- Generate unique secrets; do not leave sample or placeholder values in a live deployment.
- Expose only the n8n entry point to the public network.
- Keep sandbox containers off the public internet.
- Document how sandbox certificates are generated and how they will be regenerated after rotation or loss.
- Apply host and container updates on a schedule, with a rollback plan.
- Back up both the database and any persistent n8n volume, then rehearse a restore.
Method 3: run n8n with standalone Docker
The standalone Docker page describes a container that runs n8nio/n8n, maps host port 5678, sets timezone variables, enforces settings-file permissions and persists /home/node/.n8n in an n8n_data volume. That volume is what keeps configuration and data when the container is recreated.
The page is explicitly marked outdated and directs readers to Docker Compose. It is therefore most useful for local development, testing or maintaining an existing container arrangement, not as the default for a new production deployment.
Database and production limitations
Standalone Docker defaults to SQLite. It can be configured for PostgreSQL with DB_TYPE=postgresdb and the related database environment variables, but a database setting alone does not provide a complete production architecture. You still need durable storage, controlled networking, secrets management, TLS, backups, monitoring, upgrade procedures and a recovery plan. The documentation warns that the simple standalone approach is not safe for production without that fuller setup.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
When to move from standalone Docker to Compose
Move to Compose when you need multiple coordinated services, explicit networks and volumes, repeatable upgrades, a sandbox stack, a managed database or integration with another application. Compose makes those relationships visible and reviewable instead of hiding them in a one-off container command.
Free tools Windows power users keep installed
One-click scans. No signup required.
Method 4: install n8n with npm
The official install index still lists npm, but current guidance changes how new users should interpret that option: from n8n 3.0, n8n is distributed only through Docker. Existing npm installations continue to work for now, while new installations and future upgrades should use Docker.
What existing npm users should do
- Do not remove a functioning installation solely because the distribution policy changed.
- Before upgrading, check the current official documentation for supported Node.js and npm versions and the migration path.
- Record the current n8n version, environment variables, credential storage, database configuration and process manager.
- Test a Docker-based replacement separately before switching production traffic.
Because the current npm detail page is not a reliable basis for a new command here, this article does not provide an unverified npm install command. For a fresh installation, follow the Docker-based method that matches your operational needs.
Method 5: self-host n8n through a cloud provider
Cloud-provider deployment gives you an account and infrastructure that you control while still requiring you to operate the application. n8n documents routes for DigitalOcean, Heroku, Hetzner Cloud, Google Cloud Run, AWS, Azure, Google Kubernetes Engine and OpenShift Local, as well as generic Docker Compose guidance.
For a self-hosted n8n deployment, install n8n yourself on an Antihost VPS; its Linux VPS offers full root access, NVMe storage and unlimited traffic on a 1 Gbps port in the USA East, Netherlands and Ukraine.
What you gain
- Control over the cloud account, region, network and surrounding services.
- Freedom to select virtual machines, managed databases, container platforms or Kubernetes according to your architecture.
- Ability to apply your organization’s identity, logging, firewall and backup standards.
What you must operate
- Server or container sizing and scaling.
- Private networking, ingress and TLS certificates.
- Database provisioning, upgrades, backups and restore testing.
- Persistent volumes and retention policies.
- Monitoring, alerting, patching and incident response.
- n8n configuration, secrets and workflow-level access controls.
Provider tutorials differ in networking, storage, load balancing and certificate handling. Treat a provider recipe as an implementation for that provider rather than a portable standard. If you cannot confidently own these tasks, managed n8n Cloud avoids the infrastructure burden.
Method 6: use n8n Cloud
n8n Cloud is managed hosting: n8n hosts the instance, so you do not set up or maintain the server, container runtime, database or network. You create an account, choose a plan and work in the hosted workspace.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Trial terms
The free trial lasts 14 days. It provides Pro features, a 1,000-execution limit and Starter-level computing power. At the end of the trial, the workspace is deleted unless you upgrade. n8n allows workflows to be downloaded for 90 days after expiry, so export what you need before that recovery window closes.
Choosing a paid plan
After the trial, the available choices are Starter, Pro and Enterprise. Prices and plan limits can change, so use the current plan page when budgeting rather than relying on a fixed figure in an article. Compare execution allowance, computing capacity, collaboration and support requirements against the workload you expect.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWho should choose Cloud
Cloud is the practical default for teams that want to build workflows without becoming responsible for operating servers, TLS, database maintenance, backups and upgrades. It is also a good fit when a short-lived experiment should not leave behind a host that someone must patch and monitor. The trade-off is less infrastructure-level control than a deployment in your own account.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Production design: persistence, security and operations
Make data durable
Containers are replaceable; workflow definitions, credentials, execution history and configuration are not. Confirm which Docker volume or database stores each class of data, include those stores in backups and verify that a new container can reconnect to them. A backup that has never been restored is only an assumption.
Plan the database around usage
SQLite reduces setup friction and is appropriate for trying n8n or a small personal instance. PostgreSQL is the documented direction for teams and production workloads, particularly when several users or continuously running workflows are involved. Keep the database on a protected network and monitor storage, connections and backup completion.
Protect the network boundary
Expose only the n8n endpoint. Keep sandbox API, runner and certificate-generation services on internal networks. Put TLS in front of any public deployment, restrict administrative access at the firewall and avoid publishing database ports. Review outbound access as carefully as inbound access because workflows can call external systems.
Recommended Free Tools
Manage secrets and certificates
Replace every example secret with a unique, generated value and limit who can read environment files and volumes. Document certificate generation and regeneration for sandbox services. Rotate credentials according to your organization’s policy and test that workflows continue to authenticate after rotation.
Upgrade without losing service
Read the release notes and current installation guidance before upgrading. Back up the database and persistent volume, record the current image and configuration, then upgrade in a maintenance window. Keep a rollback path that includes the previous image and compatible database backup. For the generated setup, the supported upgrade invocation is curl -fsSL https://get.n8n.io | sh -s -- --upgrade.
Observe and test the system
Use docker compose ps to see whether services are running and curl -sf http://localhost:5678/healthz to check the n8n HTTP health endpoint in a Compose deployment. Add host, container, database and workflow-level monitoring for a production service. A green process status does not prove that external credentials, webhooks, queues or scheduled workflows are functioning, so include representative workflow tests in your checks.
Troubleshooting common installation problems
The one-line command fails immediately
Check that Docker is installed, the daemon is running and the Compose v2 plugin is available. The one-line guide is not designed around the older standalone docker-compose binary. If the machine cannot run Docker, use a different host or choose n8n Cloud.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The browser cannot open port 5678
Confirm that the services started and that you are using the host where Docker is running. For Compose, inspect with docker compose ps and test locally with curl -sf http://localhost:5678/healthz. If you are connecting from another computer, localhost refers to that other computer; use the server’s hostname or address only after configuring firewall and TLS rules.
Data disappears after a container recreation
The container was likely started without the documented persistent volume or the volume was removed. The standalone arrangement uses an n8n_data volume for /home/node/.n8n; the one-line setup uses the project directory and an n8n-data volume. Verify the volume mapping before rebuilding and never use down -v unless deleting data is intentional.
The stack starts but production performance is poor
Check memory and CPU against the documented 4 GB RAM and 2 vCPU baseline for the sandbox Compose stack, then examine workflow concurrency, execution history and database load. If the instance has grown beyond a small personal use case, move from default SQLite to PostgreSQL and design a scaling and backup strategy rather than only adding container restarts.
Sandbox services are exposed publicly
Remove public exposure and place sandbox containers on an internal network. The documented security guidance is to expose only n8n through the firewall. Review published ports, cloud security groups and reverse-proxy routes before reconnecting the service.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →An npm installation needs an upgrade
Do not assume an old npm command remains supported. Record the existing environment, consult the current official documentation and plan a Docker-based migration for new n8n 3.0-era deployments. Test the replacement with a copy of the data before changing the live instance.
Quick Recap
A practical decision checklist
- Choose the one-line setup when you need a new self-hosted instance quickly and the generated SQLite-based stack is sufficient.
- Choose hand-built Compose when you need to edit services, use PostgreSQL, integrate with another Compose project or apply a deliberate production topology.
- Use standalone Docker only for local development, testing or an existing arrangement that you understand; the current documentation points new users to Compose.
- Keep npm only as an existing-install or legacy path and verify current support before changing it.
- Choose a cloud-provider deployment when your team can operate networking, TLS, databases, backups, monitoring and security in its own account.
- Choose n8n Cloud when eliminating infrastructure maintenance is worth giving up some low-level control, and account for the 14-day trial, 1,000-execution limit and expiry behavior.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
