Architecture
Repository Map
Learn how the Noderax repos are split and what each one owns in the shipped product.
Repository Map
The working tree is made of coordinated repos, not a single package workspace.
Main repos
noderax-api: NestJS control-plane APInoderax-web: Next.js authenticated dashboardnoderax-agent: Go runtime for managed nodesnoderax-platform-release: bundle builder, installer, compose definitions, nginx configs, release metadata, and publish scriptsnoderax-saas: public marketing sitenoderax-docs: public documentation site
control-plane API, auth, orchestration, realtime, diagnostics, updates
operator dashboard and authenticated UI surface
node-side runtime for telemetry, tasks, and terminals
bundle builder, installer, compose, nginx, publish flow
marketing site
public Fumadocs site and checked-in OpenAPI snapshot
Why the split matters
The separation is operationally meaningful:
- the API and web ship together in the control-plane bundle
- the agent ships as its own release line and rollout surface
- the release repo owns bundle assembly and CDN publication
- the docs site consumes a checked-in OpenAPI snapshot instead of reaching into a live control plane
Practical implication for contributors
A product change often spans multiple repos. A new runtime behavior can require API code, web UI adjustments, release metadata changes, installer/runtime updates, and docs updates in parallel.