Noderax Docs
Start Here

What Is Noderax

Understand the current Noderax product surface, its deployment model, and how the main repos map to user-facing capabilities.

What Is Noderax

Noderax is an infrastructure operations platform built around a single control plane and a node-level agent runtime.

The shipped system combines:

  • a web control plane for platform admins and operators
  • a NestJS API that owns orchestration, persistence, auth, realtime, and updates
  • a Go agent installed on nodes to stream metrics, run tasks, open terminals, and report progress
  • an installer-managed platform bundle that packages web, API, nginx, PostgreSQL, Redis, and runtime helpers into a self-hosted deployment

Product surfaces

Control plane

The control plane is what users log into. It includes:

  • workspaces, teams, memberships, and roles
  • node enrollment and bootstrap flows
  • metrics, events, diagnostics, packages, scheduled work, and notifications
  • terminal sessions and transcript handling
  • agent update rollouts
  • installer-managed control-plane updates

Agent runtime

The agent is installed on each managed node. It:

  • authenticates against the control plane
  • streams metrics and heartbeat state
  • accepts tasks and package actions
  • opens reverse terminal sessions
  • reports node install/bootstrap progress

Installer-managed self-hosting

The platform bundle is not a thin compose example. It is an opinionated runtime packaging layer that:

  • provisions the first-run setup stack
  • promotes into the HA runtime after /setup
  • manages bundled nginx and certificate renewal
  • exposes control-plane self-update actions from the dashboard

The self-hosted product has two distinct phases: the setup phase with api-setup, then the installed HA runtime with api-a, api-b, web, and nginx.

Repository map

NestJS control plane API
Next.js operator dashboard
Go node agent runtime
bundle build, installer, compose, nginx, publish scripts
public marketing site
this docs site

Deployment model

Noderax currently documents and optimizes for:

  • installer-managed self-hosting
  • English-only public docs
  • current-line docs plus changelog
  • release identity driven by releaseId

The installer-managed path is the one most operational documentation assumes.

On this page