Nod Runtime
Nod Runtime is a filtered Docker API gateway that is one component of the self-hosted Nod stack.
Platform availability
Available on 3 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.
76/100 Good
- Maintained
- 91last commit 1 day ago
- Popular
- 692,740 GitHub stars
- Easy to install
- 553 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 2,740
- Open issues
- 123
- Last commit
- 2026-11-20
- Latest release
- nod-v0.9.0
- License
- Apache-2.0
- Activity
- rising
Checked 2 days ago - source: GitHub (n8n-io/nod)
Resources & Compatibility
Requirements not published yet.
Checked 2 days ago - source: Docker Hub image tags and published docs
First-install notes
- Use HTTPS for a self-hosted bundle If you are installing a self-hosted bundle, run sh install.sh --https so Caddy (the web server that manages certificates) can obtain and renew the HTTPS certificate. Keep using --profile https when operating the installation later, or secure web access may break. source
- Keep settings and data outside the bundle Once your installation is running, keep the .env settings file and data volumes (the Docker folders that keep your files) backed up or protected. They are not inside the install bundle, so if they are lost or overwritten, Nod may start without your saved settings or files. source
- Let the first Docker start finish After your settings are ready, run docker compose up -d --build --wait and keep the terminal open until it completes. Docker Compose is the command that starts the prepared app pieces, and the first build downloads needed tools, so stopping early can leave Nod incomplete. source
Fetched 2 days ago - each note links to its source
Variants
Alternatives (12)
- Activepieces - Activepieces is a self-hosted, open-source no-code workflow automation platform.
- Apache Airflow - Airflow is a platform to programmaticaly author, schedule and monitor data pipelines.
- Automa - Automa is a browser extension for automating repetitive web tasks by connecting visual blocks into workflows.
- Automatisch - Automatisch is a business automation tool that lets you connect different services like Twitter, Slack, and more to automate your business…
- Cronicle - Cronicle is a self-hosted, multi-server task scheduler and runner with a web interface that executes scheduled, repeating, and on-demand jo…
- Directus - An Instant App & API for your SQL Database.
- 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.
- Huginn - Huginn is a self-hosted automation platform for building custom agents that monitor online sources, react to events, and take actions on yo…
- IFTTT - Automates over 1000 apps and devices with non-coding integrations and partnerships with 900+ brands, creating a billion Applets monthly.
- Kestra - Kestra is an open-source, event-driven, language-agnostic orchestration platform that lets teams schedule and manage data, AI, and infrastr…
Checked 2 days ago - source: AlternativeTo
Common questions
How can I reach a self-hosted Nod server from other devices?
Use an SSH tunnel or a domain with inbound ports 80 and 443 for HTTPS.
Should I disable the workspace firewall when running Nod on a cloud VM?
Keep the workspace firewall enabled. Cloud VM metadata services can provide cloud credentials to workspace commands, so also configure your provider's metadata access controls.
What should I retain with my backups for a self-hosted Nod install?
Keep the downloaded bundle with your backups. Check the full source commit in the release.
Answers sourced from nod.n8n.io
Community
No community discussions collected yet.
