Every NestJS project starts with the same shopping list: authentication, permissions, file uploads, audit logs, notifications, slugs, tags. Nestbolt ships those as small, focused, well-tested packages so your team can spend its time on the product instead of the plumbing.
After shipping enough NestJS apps, the same pattern shows up: a new project, and the first two weeks go to the boring stuff — wiring auth, designing a permissions system, hand-rolling a media uploader, building an audit log that nobody trusts.
Most of that work is not where the product lives. It's infrastructure that should already exist, configured the way a senior engineer would configure it on day one.
Nestbolt is that toolbox. Each package is small, opinionated where it matters, and unopinionated where it shouldn't be — database-agnostic boundaries, optional event emitters, decorators that compose. The goal is simple: pull in the package, configure it once, and get back to building the thing that actually makes your app yours.
Each Nestbolt package solves a single problem end-to-end. No grab-bag mega-modules, no surprise dependencies.
Every package follows the same pattern: forRoot/forRootAsync, decorators, mixins, and typed services. Learn one, learn them all.
Race-safe writes, idempotent operations, optional events, and database-agnostic boundaries — built the way you'd write it on a real project.
All packages are MIT-licensed and developed in the open on GitHub. Use them anywhere — personal projects, startups, or enterprise.
Nestbolt is built and maintained by one person, in the open.
Software Engineer · Open-source maker
Software engineer working primarily on backend systems and developer tools. Creator of merakiui.com, co-founder of tailwindcomponents.com, and the maintainer of every Nestbolt package. Spends most of his time turning the boring parts of building software into things other people don't have to build again.
Browse the packages, drop one into your NestJS app, and ship the features that actually matter to your users.