About
Hey community! 👋
I'm Dharmendra Jagodana, and I build BuildBase with my brother.
Why this exists
I don't come at this as an "auth company." I come at it as someone who kept building SaaS products and kept hitting the same wall.
Five of my products are live right now:
Imejis - template-based image-generation API
AgentCenter - mission control for AI agents
PlugNode - visual AI workflow builder
RemoteWait - virtual queue system
LinkTracer - creator analytics
For every one of them, before I could build the actual idea, I had to rebuild the same backend from scratch: sign-up and login, Stripe billing, multi-tenant workspaces, roles and permissions, usage limits, emails, notifications, webhooks. Weeks of plumbing, every time, that had nothing to do with what made the product special.
After the third rebuild I started extracting it. After the fifth, it was a platform. That's BuildBase.
What it is
The SaaS backend for React / Next.js, in one SDK (npm install @buildbase/sdk). Not just auth - 19 integrated modules that actually talk to each other:
Auth - email/password, magic link, passkeys (WebAuthn), Google, GitHub, Microsoft, LinkedIn, and a full OAuth 2.0 server
Billing - Stripe, bring your own account, usage-based metering + quota enforcement + credit system + subscriptions
Multi-tenancy - an isolated workspace (and isolated database) per org, with RBAC
Workflows - a real event-driven engine: triggers, actions, conditions, queue-backed
Communication - email with your own sender (SMTP, Google, Microsoft, Mailgun) + notifications, including real-time Slack alerts
Growth - feature flags, audience/CRM, short links, webhooks, analytics
Global - i18n across 8 locales, multi-currency
Headless - an API layer, so you can use any of it without our UI
…and more.
What makes it different (the part I care about)
Bring your own Stripe, 0% platform fee. Your customers pay you directly, into your own Stripe account. I never touch your revenue. The norm in this space is that your bill climbs as you grow - I built the opposite on purpose.
You own your data. Two ways to run it today: Shared (an isolated DB per app on our infra) or Self-hosted (run our Docker images on your own servers with your own MongoDB + Redis). A Dedicated per-app infra tier is coming. No lock-in.
Per-app pricing. One app = one org = one isolated database, so you never pay for scale you're not using. Three plans: Launch, Grow, Scale.
Let me be straight about where it's at
I'd rather you hear this from me than dig for it:
React / Next.js only today. No Vue, Svelte, or native mobile SDK yet (soon…).
Not open source. Self-hosting means running our compiled Docker images on your own infra - you don't get the source. What you get instead is no vendor lock-in. I know a lot of this crowd values OSS; I'm not going to pretend to be something I'm not.
Early and bootstrapped. It's me and my brother. The SDK is young (v0.x). But it isn't vaporware: I run five real products on it in production, every day.
Who it's for
Solo founders, vibe coders, and small teams building SaaS on React / Next.js who are sick of wiring the same backend together for the tenth time and want their weeks back for the actual product.
Try it / tear it apart
Live demo: https://demo.buildbase.app
Docs: https://docs.buildbase.app/introduction
Self-host starter: https://github.com/buildbase-app/self-hosted-starter (Learn: https://www.buildbase.app/self-hosted)
Claude Skill: https://github.com/buildbase-app/claude-skill
I'll be here all day. The feedback I most want: what would make you trust a backend SDK enough to build your next SaaS on it? And what's the one thing missing for your stack?
Reach me anytime at dharmendra@buildbase.app