Nod Browser
Nod Browser is the headless web-browser container in the Nod self-hosted AI assistant, where Nod Server drives it via Nod Runtime to complete web tasks on…
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
- Start the stack with Docker Compose Run `docker compose up -d --build --wait` in the install folder and wait for it to finish. The first build downloads the browser tools the app needs, and stopping early can leave the app half-started. source
- Use the HTTPS setup if others will connect Start the bundle with `sh install.sh --https` and keep using the HTTPS profile when operating it. Caddy (the built-in web proxy) handles the certificate, so secure URLs keep working without manual renewal. source
- Keep the container name Keep the container name as 'nod-browser'. Nod Server and Nod Runtime resolve the browser container by name, so renaming it will break the stack. 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
Can the self-hosted Nod server be exposed over my own domain instead of using SSH?
Yes. Remote access can use an SSH tunnel, or a domain with inbound ports 80 and 443 for HTTPS.
Do I need a model API key before installing the server?
No model key is needed to install the server. You connect a model after startup.
What cloud-VM metadata setting should I enable for self-hosted Nod?
Keep Nod's workspace firewall enabled and configure your provider's metadata access controls. Cloud VM metadata services can provide cloud credentials to workspace commands.
Answers sourced from nod.n8n.io
Community
No community discussions collected yet.
