boilerplate_backend
A backend foundation, built for coding agents.
Describe your data model, and get a working API: entities, repositories, services, and controllers, with real database queries rather than stubs. It's Node.js and TypeScript on Firebase, and it's the foundation most of our own products run on.
The foundation isn't copied into your project and left to age. It ships as npm packages, so when we fix or improve it, your project takes the update like any other dependency.
How it works
Scaffold
One command sets up the project: your Firebase project, the features you want, and only the utility packages you choose.
Describe your data
Write the data model in plain, declarative TypeScript: entities, fields, relationships, and which fields to encrypt. It's a format a coding agent can read and write as easily as a person.
Generate and ship
The generator writes each layer from the model, importing from the packages rather than copying them. Then you write the business logic, which is the part that's actually yours.
Updates arrive by npm
Most boilerplates are a starting point you fork and then maintain alone. This one is two parts: packages for the code that runs, and a command-line tool for the project's structure. Run npm update for the packages, and sync for the structure, and every project built on it moves forward together.
Only what you need
Around two dozen utility packages, each installed on its own:
- Logging that strips personal data, and an event bus
- Email, SMS, and push notifications
- CRM, ERP, and work-management connectors
- One interface over OpenAI, Claude, and Gemini
- Caching, tokens, validation, and time zones
Secure by default
A generated route needs a signed-in user unless you mark it public. Access checks deny unless a rule allows. List endpoints cap their page size. Personal data is encrypted with authenticated AES-256-GCM.
The secure option is the default, so a coding agent that does nothing special still gets it right.
Two kinds of encryption
Identity and client content need different protection, so there are two packages. One encrypts personal data under a key your product holds, so it survives as long as your records do. The other encrypts content under a key per record, so destroying the key erases the content. It's the same package our own products use.
Get started
Scaffold a new project:
npx @xbg.solutions/create-backend init The code is public on GitHub, under the Business Source License 1.1.
Often goes with
For the front end, boilerplate_sveltekit follows the same pattern, and the two run side by side in one project.
Ready for a conversation?
No sales pitch. No obligation. Just a chat about what you're building and where the opportunities might be.