GitHub - Production-ready SaaS boilerplate to ship in hours.
by•
Production-ready Multi-Tenant SaaS Platform built with Nuxt 4, Supabase, PostgreSQL RLS, PWA, AI-ready architecture, and full Arabic/English localization. - Ibrahem3/burhan-platform
Replies
Best
Maker
📌
Hey Product Hunt! 🚀
I got tired of spending weeks rebuilding the exact same infrastructure every time I wanted to launch a new SaaS—setting up Auth, configuring robust multi-tenant isolation, wiring database routers, and cleaning up boilerplate layout code.
So, I locked myself in a room and built this Production-Ready SaaS Chassis in just 48 hours to solve my own problem. I stripped away all the friction so you can just drop your business logic and ship.
It already drove some insane validation locally (with 90k+ views and hundreds of developers cloning it in just a few days), so I decided to open-source it and give it to the world.
I’m here live today. Grab the repo, break it, test the multi-tenancy, and let me know your thoughts or what features you want me to drop next. Let’s ship! 🛠️
Report
Congrats on shipping this. One thing that would make a real difference for teams picking it up: a built-in billing module with usage metering and plan limits. Most multi-tenant projects need this early, and wiring Stripe or Paddle into the Supabase schema with quotas per tenant saves a ton of repeated setup work. Could be a simple template the community extends.
Spot on, Asel! You’ve pointed out the absolute holy grail of SaaS boilerplates.
Wiring usage-based billing (like Stripe/Paddle) into Supabase RLS quotas is indeed where most developers hit a wall. I wanted to keep this initial chassis extremely lightweight and unopinionated about payment gateways, but adding a modular billing/metering template is definitely the logical next step.
Since Burhan is fully open-source, I’d love to see the community drive this. If anyone wants to collaborate on a PR for a robust Stripe/Paddle schema integration, the repo is open and ready for it!
Thanks for the solid feedback! 🚀
Report
The multi-tenant setup with Postgres RLS right out of the box is genuinely impressive, saves so much boilerplate work. Curious how the Arabic/English localization handles mixed content though.
Hi Ebru, the exact answer to your question is already fully documented in the GitHub README (under the "Omni-Channel Content Engine" and "Project Structure" sections).
It seems you haven't actually opened the repository link yet! Go ahead, check out the README, and let me know if you have any real feedback once you've actually looked at the code and documentation. 🚀
Replies
Congrats on shipping this. One thing that would make a real difference for teams picking it up: a built-in billing module with usage metering and plan limits. Most multi-tenant projects need this early, and wiring Stripe or Paddle into the Supabase schema with quotas per tenant saves a ton of repeated setup work. Could be a simple template the community extends.
@aselnorgaz93673
The multi-tenant setup with Postgres RLS right out of the box is genuinely impressive, saves so much boilerplate work. Curious how the Arabic/English localization handles mixed content though.
@ebru1lid