Nora

Run OpenClaw and Hermes fleets on your own infrastructure — from one control plane.

OpenClaw + Hermes  ·   Docker + Kubernetes GA  ·   69 provider connections  ·   Apache-2.0

📚 Documentation · Self-Hosting · Architecture · How Nora Compares · Press Kit · Changelog

_{▶ Watch the walkthrough}

What Is Nora?

Nora is the self-hosted AI agent ops platform for running autonomous agent fleets on infrastructure you control — whether you standardize on OpenClaw, Hermes, or keep both available in the same operator surface.

Most teams running agents in production eventually rebuild the same layer around the runtime itself: deploy workflows, secrets, monitoring, logs, terminal, templates, and a separate admin surface. Nora exists so that layer doesn't have to be rewritten every time the runtime conversation changes. Operator workflows live under /app; platform-wide admin lives under /admin.

→ Why Nora · Runtime model · Deployment footprint

Features

• Deploy & operate runtimes — provision OpenClaw and Hermes agents to Docker or Kubernetes (both GA, official Helm chart) with full lifecycle controls: deploy, start/stop, restart, redeploy, and version history.
• Migrate existing runtimes — recreate agents from uploaded bundles, with privileged local-Docker Live Pull available to self-hosted platform admins.
• Live operator access — streaming logs, an interactive terminal into running containers, a file browser/editor, and the OpenClaw gateway & Hermes dashboard embedded in the operator UI.
• Monitoring & alerting — per-agent metrics and cost, a fleet needs-attention roll-up (errored, stuck, over-budget, stalled telemetry), and user-defined alert rules delivered to your channels.
• Budgets & scheduled runs — per-agent LLM budget hard caps with auto-pause, plus recurring cron schedules for agent runs with queue retries and sweep guards.
• Secrets that fail closed by default — provider keys are AES-256-GCM encrypted at rest and synced to running runtimes; production refuses to boot without a valid encryption key unless an operator deliberately enables the insecure plaintext override; SSH host-key pinning protects remote (BYOC) Docker hosts.
• Network isolation — baseline Kubernetes NetworkPolicy ingress isolation with admin-managed CIDR allow rules, and an experimental NemoClaw hardened sandbox for untrusted code.
• Agent Hub — installable, versioned starter templates to go from zero to a working agent fast.
• Integrations — a 69-entry credential/connectivity catalog (source control, chat, cloud, observability, vector DBs, automation) plus 17+ LLM providers. Executable behavior comes from runtime skills or MCP adapters; supported per-agent MCP servers are enabled explicitly.
• Experimental Proxmox LXC — deploy standard OpenClaw or a prepared Hermes image into unprivileged LXC with verified API TLS and pinned SSH. It is not VM-grade isolation and still requires the real-hardware smoke gate before production use.
• Automate everything — a public REST API (OpenAPI 3.1), the @noraai/cli, and the @noraai/mcp-server for Claude Code, Gemini CLI, Claude Desktop, and Cursor.
• Workspaces & RBAC — multi-tenant workspaces with ranked roles, a platform admin surface, account event history, and encrypted managed backups.

Screenshots

Operator dashboard	Fleet monitoring & needs-attention triage
Agent detail & lifecycle operations	Hermes WebUI embedded in Nora
Agent deploy flow

Quick Start

Requirements: macOS 12+, Linux, or Windows 10+ (WSL2), with Docker Engine + Compose v2. The installer checks for Docker, Git, and OpenSSL and installs anything missing.

macOS / Linux / WSL2:

curl -fsSL https://raw.githubusercontent.com/solomon2773/nora/master/setup.sh | bash

git clone https://github.com/solomon2773/nora.git
cd nora
less setup.sh
bash setup.sh

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/solomon2773/nora/master/setup.ps1 | iex

Windows requires PowerShell 7+. The default Windows PowerShell 5.1 is not supported — run the command above from a pwsh 7 session.

Kubernetes (Helm):

helm show chart oci://ghcr.io/solomon2773/nora

The command resolves the latest published chart; pin the reported version for reproducible production installs. The public OCI chart installs the full Nora control plane. See the Helm instructions for the required secrets and Ingress options.

The installer verifies prerequisites, generates or preserves secrets, optionally creates a bootstrap admin, picks free local ports when the defaults are busy, and starts the stack. Once it finishes, open the URL printed by setup. Local mode defaults to http://localhost:8080, but setup may select another port such as 8081 on a busy workstation. Then follow the first-15-minutes walkthrough.

No API key yet? On installations with the local Docker target enabled, choose Launch local Docker demo on the Getting Started page. Nora deploys a working agent against its built-in deterministic demo provider, so you can validate chat and the operator workflow with zero keys and zero model-usage cost. Kubernetes-only installations start by adding a model provider and deploying to an enabled cluster target.

For manual setup, environment variables, public-domain mode, TLS, Remote Docker, Kubernetes, NemoClaw, and experimental Proxmox LXC configuration, see the docs:

• Self-hosting guide
• Environment variables reference
• Provisioner backends (Docker and k3s/Kubernetes are GA; Remote Docker, NemoClaw, and Proxmox LXC are experimental)
• Remote Docker BYOC setup — SSH registration, private networking, validation, sharing, and recovery
• TLS and public domains
• Fronting a launch with Cloudflare — edge caching, rate limiting, and spike absorption for the single-host deploy

Documentation

Full docs live at docs.norafleet.ai. The MDX source is in docs/.