AI helped us build faster.
The bottleneck became consistency.
So we started building Brumkit.
Not another template.
A repeatable starting system for every SaaS.
You built it with AI in a weekend.
Cool.
Now maintain it for the next 12 months.
Speed gets you the MVP.
Systems get you the business.
Brumkit is our attempt to make every new SaaS start from the same solid foundation.
Everyone is talking about building faster with AI.
We're more interested in building the same way, every time.
✅Consistent code.
✅Consistent design.
✅Consistent architecture.
That's the idea behind Brumkit.
AI writes code.
It doesn't guarantee consistency.
>One project has great auth.
>Another has better UI.
>Third has cleaner architecture.
Eventually, you're maintaining three different products.
Brumkit fixes the starting point.
Your SaaS isn't a souvenir collection.
It's not supposed to be:
• A button from one UI kit
• A form from another
• A dashboard from somewhere else
• AI-generated code stitched together
A great SaaS feels like one system.
Same patterns.
Same language.
Same experience.
What you give is what you get is true with Ai.
Give it a messy codebase... You'll get more mess.
Give it a solid foundation... It becomes an incredible teammate.
AI made building software faster.
But also made inconsistency easier.
> Different prompts.
> Different patterns.
> Different components.
Speed isn't the bottleneck anymore.
Consistency is.
Most AI coding tools are great at generating features.
We're more interested in helping AI generate features that already fit the product.
That's the problem we're exploring with BrumKit.
@mathiasvrb We're designing BrumKit around reusable patterns instead of one-off implementations.
The goal is to give AI a predictable system to work within consistent components, layouts, naming, and architecture etc so new features extend the product instead of reinventing it.
We're building Brumkit.
Here's where we're going:
✅ Auth (done)
✅ RBAC (done)
✅ Transactional emails
🔧 Admin Panel (in progress)
A Next.js SaaS starter that covers everything , so you never build the foundation twice.
The full kit is cooking. 🍳
The biggest problem with vibe coding isn't bugs.
It's that every prompt can create a different way of building the same app.
Over time, your SaaS becomes inconsistent.
BrumKit gives AI a playbook, so every feature feels like it was built by the same engineering team.
Imagine starting your next SaaS idea with:
→ Auth already working
→ Payments already wired
→ Admin panel already built
→ Emails already flowing
→ Teams & roles already handled
→ Consistant design, everytime!
That's the Brumkit we're building.
Everyone celebrates AI for building features faster. But real challenge starts after the 50th prompt.
It's not bad code. It's inconsistent code.
We're building BrumKit with opinionated AI rules, so every new feature follows the same architecture, not a new pattern.