Nouride runs as a standalone binary with its own embedded runtime. To review the script before piping it to a shell:

curl -fsSL https://get.nouride.com/install.sh | less

By default the dashboard listens on loopback (127.0.0.1:18254). To expose it across your local network:

curl -fsSL https://get.nouride.com/install.sh | sudo sh -s -- --host 0.0.0.0

To update a native install later, use the dashboard's Update page or nouride update.

Once installed, open http://127.0.0.1:18254/ on that machine (or http://<your-ip>:18254/ if you installed with --host 0.0.0.0) to complete setup. The first-run password is printed by the installer and in the service log (journalctl -u nouride | grep -A6 'Nouride is ready').

On a Mac with Apple Silicon (M1 and later), since 0.7.20:

curl -fsSL https://get.nouride.com/install.sh | sh

It installs into ~/nouride and runs as a LaunchAgent while you are logged in. The first-run password is in ~/nouride/.nouride/data/nouride.log. Intel Macs are not a published target.

The official multi-arch image (linux/amd64 and linux/arm64) is on GitHub Container Registry. With Docker Compose:

services:
  nouride:
    image: ghcr.io/nouverse/nouride
    container_name: nouride
    restart: unless-stopped
    ports:
      - "127.0.0.1:18254:18254"
    volumes:
      - ./nouride:/app/.nouride

The port is published on the host's loopback only, as a native install listens: open the dashboard on the machine itself, or tunnel to it from yours with ssh -L 18254:127.0.0.1:18254 you@your-server. To reach it from other machines, drop 127.0.0.1: ("18254:18254"): the dashboard then answers anyone who can reach the host, and a port Docker publishes goes around a firewall such as ufw. For a public address, keep it on loopback and put a reverse proxy with TLS in front of it on the same machine (Caddy, nginx, a Cloudflare Tunnel).

Agents install system packages in the container too: docker exec nouride nouride pkg install <name>, or an agent asks, and you approve each change unless the agent is trusted. What they installed is kept on the volume and installed again when the container is recreated, as every update does; nothing the image ships can be removed. NOURIDE_SYSTEM_PACKAGES=off turns it off.

To update, pull it again and recreate the container. The volume keeps everything:

docker compose pull && docker compose up -d

To check your configuration against a new image before you switch:

docker run --rm -v ./nouride:/app/.nouride ghcr.io/nouverse/nouride nouride config check

An install older than 0.7.28 updates in two steps: Updating has how.

Every install carries the Nougate LLM gateway in the same process: model calls answered from inside the daemon, with no second container and no network hop. It stays off until you choose Use Nougate in setup, or turn it on from the dashboard's LLM Gateway page; then setup signs in to a Claude, ChatGPT, Copilot, Gemini or Kiro account you already have instead of asking for an API key. Off, it costs about 1.3 MB of memory.

On, it listens on port 18256 and keeps its state (accounts, providers, nougate.db) in a folder of its own inside the same volume: ./nouride/nougate/data/. Publish 18256 only for other tools that call it with a gateway key. To point a provider at it by hand, in .nouride/config.toml:

[providers.local]
kind = "openai"
base_url = "http://127.0.0.1:18256/openai/v1"   # or /anthropic/v1

Coming from the Router edition? Router is part of Community since 0.8.28. A Router install updates onto Community by itself and keeps Nougate on. Until 0.9 the nouride-router image still receives each release; change image: to ghcr.io/nouverse/nouride whenever you like before then.

Standalone tarballs include the executable, built-in skills, example configuration and the dashboard. Download the latest directly, or browse every version on the Releases page.

Alpine / musl: the -musl build needs libstdc++ (apk add libstdc++).

Every release carries its checksum file, signed: CHECKSUMS, with its .sig. The installer checks both before it installs anything.