In active development toward v1.0 Coming soon
Nexuq
A headless, multi-tenant e-commerce engine for the .NET 10 ecosystem: a modular monolith with hard internal boundaries, a split JIT and Native AOT host model, PostgreSQL-first persistence, and a production reference storefront built with Next.js.
Architecture
Nexuq splits its runtime into two hosts. A JIT host serves mutations and the full engine; a Native AOT host serves high-throughput storefront reads. Tenancy is enforced end to end: tenant resolution middleware, schema-based tenant provisioning, and live PostgreSQL row-level security coverage.
What works today
Commerce core
- Product catalog, category reads, and cart composition
- Cart mutations with customer-ownership checks
- Checkout with tenant-scoped audit events and fail-closed payment compensation
- Stripe webhook persistence with idempotent refund handling
Tenancy and isolation
- Schema-based tenant provisioning with live PostgreSQL RLS coverage
- Tenant-isolated caching with fail-safe behavior under chaos testing
- Immutable audit foundation with a mutation-revoking bootstrap
Search
- pgvector semantic embeddings beside full-text keyword retrieval
- Reciprocal-rank fusion of both candidate sets
- Controlled fallback when the search backend is unavailable
Identity and security
- Registration, login, and refresh-token rotation with replay revocation
- JWT algorithm-confusion rejection, CSRF guards, and rate limiting
- SSRF and open-redirect protections, upload validation, structured security logging
Storefront
- Next.js reference storefront: registration, cart, checkout confirmation handoff
- Playwright end-to-end coverage in CI
- Agent-ready metadata endpoint describing read-only capabilities
Verified on every merge
- CycloneDX SBOM generation and license verification
- OWASP ZAP baseline scan
- k6 load test: 1,000 virtual users on storefront reads
- Lighthouse gate: 95+ performance, accessibility, best practices, SEO
What is still ahead
Remaining production hardening across commerce modules, full hosted Stripe checkout and additional payment providers, customer account pages, promotions, multi-currency, production semantic search, and release packaging are planned but not finished. The storefront checkout flow is deliberately fail-closed today while the final order contract is implemented.