Every developer knows the absolute worst part of starting a new software project.It isn't writing the features, designing the UI, or talking to users. It’s the mind-numbing, repetitive grunt work of wiring up the baseline infrastructure before you can write a single line of business logic.You open a blank IDE and immediately spend 20 hours trying to make Next.js talk to FastAPI, debugging environment variables across different programming language runtimes, routing auth webhooks through Clerk, and testing payment handshakes.By the time the app finally compiles, you've burned a week of billable time.
The Problem with "Opinionated" Boilerplates
To fix this, we buy boilerplates. But the current market leaders are broken. They sell static, rigid templates tightly coupled to one single tech stack (usually Next.js + MongoDB + Stripe).If a client or an MVP requires you to swap to a high-performance Python backend or a lightweight SvelteKit frontend, that $250 boilerplate shatters. You have to tear the codebase apart and start from scratch.A boilerplate shouldn't be a pre-furnished house that forces you to live with the creator's messy code opinions. It should be a pristine, adaptive launching pad.
What I am Building: The DevEngine Matrix
I am currently engineering DevEngine Labs—the world’s first combinatorial software scaffolding engine.Instead of writing static templates by hand, I am building a proprietary, black-box orchestration compiler. It treats software frameworks like modular Lego bricks. By enforcing strict, decoupled boundaries between layers, the engine can take isolated modules and compile them into every mathematically possible full-stack combination on demand. My goal? Total cross-language architectural freedom.I am currently expanding the core module matrix across:
4 Frontend Frameworks: Next.js, SvelteKit, Nuxt (Vue), and React SPA
4 API Backend Runtimes: Express, FastAPI (Python), Fastify, and NestJS
2 Authentication Systems: Clerk and NextAuth
2 Global Payment Gateways: Stripe and Lemon Squeezy
File Tree example:
Folder PATH listing
C:.
│ package.json
│ README.md
│
├───adapter-stripe
│ │ package.json
│ │ srcindex.ts
│ │
│ └───src
│ index.ts
│
├───backend-fastapi
│ main.py
│ package.json
│ requirements.txt
│
├───frontend-nextjs
│ │ next-env.d.ts
│ │ package-lock.json
│ │ package.json
│ │ srcappapiedge-handlerroute.ts
│ │ tsconfig.json
│ │
│ └───src
│ └───app
│ └───api
│ └───edge-handler
│ route.ts
│
└───shield-clerk
│ package.json
│ srcindex.ts
│
└───src
index.ts
When these modules run through the compiler, it automatically outputs 128 completely distinct, production-ready full-stack starting grids.
Phase 2: The Database Expansion Loop
Because this is an automated matrix, adding a module doesn't add one feature—it multiplies across the entire system. Next up, I am hand-verifying modular database and ORM integration layers for Prisma, Drizzle, native PostgreSQL, and MongoDB. The moment those modules drop into the compiler, the library instantly quadruples from 128 combinations to 512+ pristine full-stack permutations. No tech lock-in. No bloated boilerplate code. You select your exact tech setup, the engine compiles it securely in milliseconds, and hands you a tailored, dependency-isolated ZIP.You unzip, drop your API keys, and couple the code exactly how you want once you start building.
Building in Public
Maintaining 512 variations manually is an engineering nightmare. Doing it through an automated, serverless compilation pipeline changes the economics of software manufacturing entirely. It allows me to completely undercut the over-priced, rigid template market and offer custom, pristine codebases at lightning speed.The architecture engine is built. The security perimeters are locked. The database injection scripts are running.I am building the ultimate developer tool platform to automate the infrastructure grind forever.If you want to stop fighting opinionated templates and track the launch of the infinite scaffolding factory, follow along. The engine goes live soon.
Top comments (0)