Node-Red
Node-RED is a low-code programming tool for building event-driven applications by wiring together hardware devices, APIs, and online services.
Platform availability
Available on 7 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
90/100 Excellent
- Maintained
- 100last commit 8 days ago
- Popular
- 8823,850 GitHub stars
- Easy to install
- 857 install platforms, install notes, Docker image
- Light to run
- 100256 MB minimum RAM, runs on ARM
- Security check
- 72no serious findings, 4 minor, CI, tests, OpenSSF Scorecard 6.5/10
Availability: platform listings confirmed today, links checked yesterday
- GitHub stars
- 23,850
- Open issues
- 356
- Last commit
- 2026-11-13
- Latest release
- 5.0.9
- License
- Apache-2.0
- Activity
- steady
Checked 5 days ago - source: GitHub (node-red/node-red)
Resources & Compatibility
Minimum requirements: 256 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Keep your flows and settings safe Start the container with a named volume (a Docker storage area) at /data and expose port 1880 (the web editor port). This keeps your flows and settings when the container is removed and lets you open the editor in a browser. source
- Set your own credentials secret Put your own credentialSecret value in /data/settings.js before entering passwords or API keys in flows. Without it, Node-RED uses a container-generated key, and if that key disappears you may have to delete the credentials file and re-enter everything. source
- Match the data folder permissions Make the host folder used for /data owned by the same user and group IDs the container runs as, usually PUID/PGID (the user and group IDs the container runs as) 1000 if not changed. If the ownership is wrong, Node-RED may start but cannot save flows, settings, or credentials. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (10)
- Automa - Automa is a browser extension for automating repetitive web tasks by connecting visual blocks into workflows.
- Flow-Like - Flow-Like is a source-available, self-hostable development platform for developers and technical teams to build applications, automated wor…
- Flowise - Flowise is an archived, open-source, low-code platform for developers to build LLM orchestration flows and AI agents without extensive code.
- Google Opal - Build, edit and share mini-AI apps using natural language.
- IFTTT - Automates over 1000 apps and devices with non-coding integrations and partnerships with 900+ brands, creating a billion Applets monthly.
- Make.com - Design, build, and automate workflows and tasks with a visual, no-code platform.
- Sim Studio - Sim Studio is an open-source, self-hosted workspace for building, deploying, and managing AI agents and workflows, connecting 280+ integrat…
- Trigger.dev - Trigger.dev is an open-source platform for building and deploying AI agents, workflows, and durable serverless functions in TypeScript.
- ioBroker - ioBroker is an open-source IoT platform that gives you a graphical web interface to configure, automate, and control your smart-home and ho…
- n8n - n8n is a self-hosted, fair-code workflow automation platform that connects 1,500+ apps and application programming interfaces (APIs) on a v…
Checked 54 days ago - source: AlternativeTo
Common questions
Which Docker volume should I use to persist Node-RED flows and settings?
Mount a named volume at /data so your flows and settings are kept when the container is removed.
What should I set before entering passwords or API keys in Node-RED flows?
Put your own credentialSecret value in /data/settings.js before adding credentials. Without it, Node-RED may use a container-generated key that can disappear, forcing you to delete the credentials file and re-enter everything.
Why does Node-RED fail to save flows, settings, or credentials after start?
Make the host folder used for /data owned by the same user and group IDs the container runs as, usually PUID/PGID 1000 if unchanged. Wrong ownership can prevent Node-RED from saving data.
Answers sourced from github.com, github.com, github.com
Community
- Node Red - Reddit (reddit)
- nodered - self-hosted open-source Zapier/IFTT : r/selfhosted - Reddit (reddit)
- Who's using those low-code automation apps like NodeRed? - Reddit (reddit)
- Latest FAQs topics - Node-RED Forum (forum)
- Victron Community (other)
- Is it ok to use NodeRed in bigger and critical environments ... - Reddit (reddit)
Collected 48 days ago - public community threads