AnatoliiShliakhto/nexus

Nexus is an ambitious Rust infrastructure project with a surprisingly concrete foundation for something still marked alpha. The README sets a clear direction: a hybrid runtime that can route through an Axum gateway into both WASI P2 components and native services, with DPoP-bound identity, Vault-backed secret handling, SurrealDB persistence, and OpenTelemetry baked into the local stack. That could easily read as vaporware, but the repository already has a real workspace behind it: components/access, account, audit, auth, and organization; core crates like nx-error, nx-http, nx-logger, nx-i18n, nx-database, and nx-lockbox; a Dioxus console; gateway code; xtask tooling; Spin examples; and Docker Compose ops for SurrealDB, Vault, Redis, Loki, Prometheus, Jaeger, Alloy, Grafana, and MinIO.

What stood out most is the attention to cross-cutting infrastructure. The DPoP validator is not just a README bullet; it verifies proof context, token hashes, JWK thumbprints, timestamp windows, and replay protection with Redis plus a local fallback. The error and logger crates are also treated as first-class pieces of the platform, with integration tests covering error metadata propagation, proxy request behavior, i18n fallback, and log redaction. That is a good sign for a framework trying to make security and observability part of the contract rather than afterthoughts.

The biggest improvement would be tightening the adoption path. The README claims commands like cargo setup, cargo codegen, and cargo dev up, while the implementation appears to use an xtask-style command structure, so a new contributor may not know exactly which commands are currently usable. I would add a short “current alpha status” section that distinguishes implemented, experimental, and planned pieces. Also, the CI workflow is present but appears under .github/actions/workflows/ci.yml; GitHub Actions normally expects workflows in .github/workflows, so moving it would make the project’s quality signals visible. A few component READMEs are placeholders, and the repo would benefit from one end-to-end tutorial showing a generated component, gateway routing, auth, persistence, and telemetry in one flow.

Overall, Nexus has a strong architectural point of view and enough real code to be worth watching. The project will become much easier to evaluate and adopt if the maintainer narrows the first successful path for users and makes the implemented surface area unmistakable.