I Built a SaaS on Top of an Open-Source Project and My Database Punished Me for It

I didn't design my database from scratch. That's the honest truth. When I decided to build my WhatsApp Business API SaaS — targeting digital marketing agencies in India — I didn't start with a blank Postgres schema and a whiteboard. I started with a fork. Specifically, I forked Whatomate , an open-source Go-based WhatsApp platform, and told myself: "The hard part is done. I just need to add billing and org management on top." That was about six months ago. Since then, my database has quietly humiliated me in ways I didn't expect. Not dramatically — not with crashes or data loss or anything catastrophic. Just slowly, consistently, in the way that technical debt humiliates you: by making every new feature take twice as long as it should, and by making you feel stupid for not seeing it coming. This is that story. Who This Is For If you've ever: Forked an open-source project and tried to commercialize it Inherited a codebase and tried to add multi-tenancy to it Built a SaaS and skipped the