1
0 Comments

I got tired of rewriting Auth & Multi-tenancy, so I spent months building the ultimate B2B SaaS Boilerplate.

Hey fellow hackers, 👋

Every time I wanted to start a new B2B SaaS project, I hit the exact same wall. Before writing a single line of actual business logic, I had to spend months configuring the boring stuff:

Setting up multi-tenancy without leaking data.

Configuring Stateless JWT security.

Handling Database Migrations safely.

Setting up bilingual support (RTL/LTR) for the MENA region.

As a Principal Developer, I realized this "setup fatigue" kills more startups than bad ideas do. So, I decided to stop repeating myself and built the Arab Enterprise Kit (AEK).

Instead of jumping into the DevOps nightmare of Microservices prematurely, I engineered it as a strict Modular Monolith.

The Tech Stack:

Backend: Java 25 & Spring Boot 4 (Single-Schema Multi-Tenancy with Hibernate Filters).

Frontend: Angular 21 (Zoneless UI using Signals + Native Tailwind RTL).

Integrations: Stripe Webhooks, Local AI (Ollama) for zero data leaks, and JasperReports for deterministic bilingual PDFs.

I’m currently rolling this out to help other founders save ~4 months of initial setup time.

Before pushing the actual code, I documented the entire architectural decision-making process into a 37-page blueprint.

I’d love to get feedback from other technical founders here. If you are building a B2B SaaS and struggling with the initial architecture, you can grab the complete 37-page Architectural Blueprint for free here: https://mahmoudfarouk28.gumroad.com/l/sdmeap

If you want to skip the setup entirely, the full source code is also available.

Would love to hear your thoughts on Modular Monoliths vs. Microservices for early-stage SaaS! 👇

on April 3, 2026