Grit vs NestJS
Both are opinionated and both give your backend a real shape — but they draw the box differently. NestJS is a Node.js backend framework: modules, controllers, providers, dependency injection, and you assemble auth, jobs, storage, and an admin on top. Grit is a batteries-included full-stack meta-framework that generates most of that — plus a React admin and typed clients — in Go.
The short version
Reach for NestJS when you want a well-structured backend and the freedom to pick your own ORM, auth, and pieces — all in TypeScript, sharing types with a TS frontend without codegen. Reach for Grit when you'd rather generate the batteries — auth, RBAC, jobs, storage, an admin, typed web/mobile/desktop clients — from one command, and you're happy running Go behind your frontend.
Different scope
NestJS is a backend framework — it doesn't ship an admin panel, generate CRUD, or produce typed clients; those stay your job. Grit spans the stack: one command gives you a model, service, handler, Zod schema, TS types, React Query hooks, and an admin page — with the trade-off that Grit adds Go as a second language where Nest is all-TypeScript.
Side by side
| Grit | NestJS | |
|---|---|---|
| Backend language | Go (Gin + GORM) | Node.js / TypeScript |
| Typed API → client | Generated Go → TS + Zod | Manual, or a codegen add-on |
| Admin panel | Generated, Filament-like | Build it yourself |
| Full CRUD generation | One command (model → admin) | Scaffold pieces, wire the rest |
| Auth + RBAC | Built in (roles + permissions) | Add Passport / a library |
| Background jobs / cron | Built in (asynq) | Add BullMQ / a queue |
| File storage, email, cache | Built in (S3/R2, Resend, Redis) | Wire up each yourself |
| Mobile + desktop clients | Generated (Expo, Wails) | Not in scope |
| ORM flexibility | GORM (opinionated) | TypeORM / Prisma / Mongoose |
| Microservices / WebSockets | Possible, less turnkey | First-class |
Choose Grit when
- You want batteries generated for you: auth, RBAC, jobs, storage, an admin.
- More than one client will consume the API (web + mobile + desktop + admin).
- You want Go's performance and a single self-hosted binary.
- You'd rather generate CRUD and typed clients than hand-write them per model.
Choose NestJS when
- You want one language end to end and shared types with a TS frontend, no codegen.
- You want to choose your own ORM, auth, and pieces rather than accept defaults.
- You're building microservices, GraphQL, or WebSocket-heavy services.
- You want the depth of the npm ecosystem and your team is all-in on TypeScript.
The honest trade-off
Grit trades flexibility for batteries: you get a generated admin, typed clients, and wired-in auth, jobs, and storage — but in Go, a second language alongside your frontend, with GORM as the ORM and a younger ecosystem than Node's. NestJS keeps everything in TypeScript and lets you pick every piece — but that admin, that CRUD, that RBAC, and those clients are yours to build and maintain. If you value structure plus freedom of choice, NestJS fits. If you value generated batteries, multi-client output, and Go performance, Grit fits.