Repositories

Nexus is one monorepo plus a few clean satellites — not twenty repos on day one. Split out independent releases only when something truly needs it.

Git organization

github.com/nexus/nexus-platform
github.com/nexus/nexus-ui
github.com/nexus/nexus-agent-images
github.com/nexus/nexus-gitops
github.com/nexus/nexus-examples
github.com/nexus/nexus-docs

For MVP, create only three:

nexus-platform
nexus-agent-images
nexus-gitops

What each repo is

Repo	What it holds	Library reference
nexus-platform	Rust workspace: Core, worker, runner, telegram + shared crates.	axum, tokio, mongodb, async-nats, kube, teloxide, genai
nexus-ui	Next.js admin console; manages the platform via the Core REST API.	Next.js 16, React 19, Tailwind v4, TanStack Query/Table
nexus-agent-images	Docker images agents run inside.	base + rust/node/python/devops/solana toolchains
nexus-gitops	Helm charts, Argo CD apps, Flux manifests, env values, RBAC.	Helm, Argo CD, Flux, cert-manager
nexus-examples	Sample projects and agents to test Nexus safely.	per-example
nexus-docs	This documentation site.	Docusaurus 3, Tailwind v4

Monorepo layout (nexus-platform)

nexus-platform/
  apps/
    nexus-core/
    nexus-agent-runner/
    nexus-telegram/
    nexus-worker/
  crates/
    nexus-domain/
    nexus-db/
    nexus-events/
    nexus-auth/
    nexus-board/
    nexus-board-plane/
    nexus-agent-runtime/
    nexus-ai-runtime/
    nexus-memory/
    nexus-skills/
    nexus-llm/
    nexus-git/
    nexus-k8s/
    nexus-observability/
  deploy/
    helm/
    k8s/
  docs/

The design rule

Nexus Core owns orchestration. MongoDB owns state. NATS owns events. Kubernetes owns isolation. Plane owns external board visibility. Nexus UI owns administration. Agents are runtime configuration, not hardcoded code.

Read the per-repository pages for the exact crate boundaries and the libraries each one uses.