exo1 — Node and React
For B2B portals and business applications: customer and partner portals, back office and workflows.
Status
Usable (v0.1.0). Runs in the cloud in a test environment. Not yet used in a client project.
What it is for
One client per installation, with organisations built in: the client's own customers, partners or departments. Users belong to organisations with a role, and data is separated per organisation. Danish and English from the start.
Stack
- Backend: NestJS 11 on Node 24, TypeScript
- Data: PostgreSQL with Prisma 7, background jobs in Postgres (pg-boss), Redis/Valkey as cache
- Frontend: React 19 with React Router 8 and MUI components
- Contract: zod schemas shared by server and client; a typed client is generated automatically
- Login: standard OIDC, Keycloak by default, Entra ID or others by configuration
- Tests and hosting: Vitest and Playwright; DigitalOcean App Platform in the EU
What comes with it
- An architecture blueprint with the rules for every layer
- A running template project with login, organisations, roles, audit log, cache and background jobs
- An example feature through every layer, so the agents have a pattern to copy
- Automated checks: types, lint, unit, integration and browser tests
- An agent layer: rules for the AI agents, a skill for every recurring move and hooks that run the checks
- CI on GitHub and environment specs for DigitalOcean
Environments
Locally with one command: database, cache and Keycloak run in Docker. In the cloud a tst-env deployed from main, and a prd-env for production that is only updated by a release. The production environment is specified but not yet created.
Login and roles
Identity comes from the client's login system through OIDC; roles and memberships live in the application. Three organisation roles (admin, member, viewer) and a global administrator. The server enforces the permissions; the interface merely hides what you may not do.
How a project starts
A project starts from a copy of exo1 at a given version. The engineer changes logo and colours, runs the setup, builds the first feature with the agent skill add-entity and removes the example. Deviations from the blueprint are written down.
What we can show
- Built from an empty folder with one command: 27 automated tests and 2 browser flows green (19 November 2026).
- Runs in the cloud in the tst-env with login through Keycloak and test data; CI runs on GitHub on every push.
- Can be tried live in the locked area.
Not in place yet
- The production environment and the release flow have not run yet.
- Monitoring (error tracking, logs) and a security and GDPR baseline.
- Admin screens, files, e-mail and real-time are not included by default; they are added per project.
- No evaluation from a real project yet.