In short
KriyaXlabs builds back ends on NestJS 11 and Node.js, with multi-tenant data isolation, organisation-scoped roles carried in the token, audit logging on every mutation, and OIDC single sign-on with SCIM 2.0 provisioning. Crampad Enterprise runs nine applications against one such API.
A back end is where the decisions you cannot undo get made. Whether tenancy is enforced in the database or hoped for in the service layer. Whether an audit line is written by the framework or by whoever remembered. Whether the second customer costs a week or an afternoon.
Crampad Enterprise forced us to answer all of those properly. One NestJS API serves nine surfaces. Every table carries organisation isolation at row level. Six roles are scoped per organisation and travel in the token, so a user can be a teacher in one institution and an admin in another without either leaking. Every mutation, by a customer admin or by our own staff, writes an audit line.
That architecture is now the starting point for client work rather than something we design fresh each time.
What we build with NestJS
Multi-tenant APIs
Row-level organisation isolation, nestable org units, and a permission model checked in one place instead of thirty controllers.
Enterprise identity
OIDC single sign-on and SCIM 2.0 user and group provisioning, built to be switched on per customer and off by default.
Audit and compliance surfaces
Immutable audit logs on every mutation, scoped so a customer sees their own history and platform staff actions are recorded too.
Integration and job infrastructure
Webhooks, queues, scheduled work and third-party integrations that retry safely and fail loudly.
Running in production
Our own products on NestJS.
Engagements that use it
We pair it with
We choose a stack for the problem rather than the reverse. If NestJS is the wrong answer for what you are building, we will say so on the call.
Questions about NestJS
NestJSDo you build REST or GraphQL?
REST by default, because it is easier to cache, log and reason about across many client surfaces. We build GraphQL where a client genuinely needs to shape its own queries, most often when several very different front ends read the same domain.
NestJSCan you add multi-tenancy to an existing single-tenant product?
Usually, and it is one of the most common reasons companies come to us. It is a data-model migration before it is a code change, so we start with a schema and access review and give you a written plan with the risky parts named.
Everything we build on
Building on NestJS?
Thirty minutes, no obligation. We reply within one business day and share a detailed proposal within two business days of the call.
30 min · No obligation · Reply within one business day