I got tired of rebuilding auth + billing for every SaaS, so I built the whole operations layer once and dogfooded it on 4 products

Every app I started, I'd lose the first few weeks to the same plumbing before touching the actual product. Auth. Org and team management. Roles and permissions. Stripe. Usage limits. Email. Notifications. Workflows. None of it differentiates anything. All of it is mandatory. And it's nearly identical app to app.

After doing it enough times I stopped treating it as work worth redoing and bundled it into one thing. That's BuildBase - one React/Next.js SDK plus a backend that handles the operations layer of a SaaS. Then instead of writing a landing page and hoping, I built four real products on top of it and shipped them.

Here's what's actually in it. Everything below is built and running - no roadmap, no coming soon.

Auth: hosted pages (login, register, magic link), email/password, magic link, Google and LinkedIn OAuth. Org-level RBAC for your team, plus a separate workspace-level permission matrix for your end users' teams.

Multi-tenant: org → many workspaces, each with its own plan and billing. Every org gets a physically isolated database, not a shared tenant_id schema.

Billing: bring your own Stripe, 0% platform fee. Usage-based and metered billing with real-time quota enforcement - Stripe meters usage fine, the annoying part is enforcing the limit the moment a user crosses it, and that's the part this actually does. Overages, seat billing, 22 currencies, non-destructive plan versioning so a price change never breaks existing subscribers.

Workflows: visual engine, 47 triggers, 11 actions, versions, instances, logs, wait steps. The lifecycle layer you usually pay for separately.

Notifications: one event fans out to email, web push, and Slack, gated at four levels.

Plus: email campaigns on your own sender (SMTP / Google OAuth), audience/CRM, feature flags, a content layer (collections, blogs, docs, forms), i18n with 8 locales, a full headless REST API with keys, and signed outbound webhooks.

The part I actually care about: self-hosting. Most tools in this space are cloud-only. This one splits - you run the tenant server on your own infra (your MongoDB, your Redis, anywhere Docker runs), I host only the dashboard, and the two talk over ES256-signed tokens so your data never touches my servers. One Docker command, public image. Every module works identically self-hosted. For anyone who cares where their data lives, that's the whole decision.

The reason I trust any of this: the four products I run on it in production use the exact same code that ships in the SDK — PlugNode (AI generation, metered per run), AgentCenter (B2B agent platform), RemoteWait (queue system for clinics/salons), LinkTracer (creator analytics). No demo-vs-real split. If the billing breaks, my own products break first.

Stack if you care: React/Next.js, MongoDB, Redis, BullMQ, Docker, GCS, ES256.
Links:

SDK - npmjs.com/package/@buildbase/sdk
Docs - https://docs.buildbase.app
Demo - https://demo.buildbase.app/
Self-hosting - https://www.buildbase.app/self-hosted

Question for this crowd:

• if you're building a SaaS right now, would self-hosting the whole data layer actually change your decision, or is bundled-and-cloud good enough as long as it's BYO-Stripe? Trying to figure out how much the self-host angle really matters to people vs. how much I just personally care about it.