Clerk vs BuildBase: auth is one module, not a backend
Clerk added billing this year, but plans and subscriptions live in Clerk, not Stripe. Here is what Clerk vs BuildBase covers once you count metering, workflows and email.
In short
Clerk is auth and user management with its own billing product that uses Stripe only for payment processing. BuildBase is one SDK bundling auth, billing, email, workflows and RBAC. Clerk wins on enterprise SSO and framework reach. BuildBase wins once you count metering and workflows.
Clerk shipped a billing product this year. It is a real one, with its own plans and subscriptions rather than a thin wrapper over Stripe. It still does not make Clerk a backend.
The one-paragraph answer
If your problem is "I need enterprise SSO and the widest framework reach," Clerk is the better tool - it ships SAML connections and supports Vue and React Native, and we do not. If your problem is "I need auth, billing, workflows and RBAC to work together without gluing four vendors," BuildBase is the simpler path, because those pieces already share one workspace model.
What each one replaces
Clerk replaces your login screen and session management. Organizations, its B2B product, adds role-based membership and domain-verified auto-join on top. Clerk Billing, added this year, turns plans into checkout flows and entitlement checks.
One detail worth getting right, because we got it wrong in the first version of this post: Clerk Billing is not a wrapper around Stripe Billing. You connect your own Stripe account, but Clerk uses it for payment processing only. Plans and subscriptions are Clerk objects, and Clerk's own docs are blunt about what follows - "Can I see Subscriptions in my Stripe account? No." Clerk is not the merchant of record either. If your finance team already reads subscription state out of Stripe, that is a migration, not an integration.
BuildBase replaces more of the middle. It bundles eight user-facing authentication methods (email/password, Google, LinkedIn, GitHub, Microsoft, magic link, passkeys, OAuth 2.0) plus API tokens for server-to-server auth, workspaces with RBAC, subscriptions and credit metering, workflow automation, and email - all running against @buildbase/sdk in one instance. A quota belongs to a workspace, a workspace has members, a member has a role - none of that is glue you write between vendors.
Clerk Billing is real progress for Clerk, worth naming plainly: it removes one integration a Clerk user used to need, and there is more in it than this post gave it credit for in August. Seat-based plans are documented, with seat limits, per-seat pricing and a pool of included seats. So is payment-failure visibility - subscription.pastDue, subscriptionItem.pastDue and payment-attempt webhooks all exist.
What it still does not do is usage metering or quota enforcement. Unit pricing is there, but the docs describe it in terms of seats, not consumption, and nothing documents metered usage. Nor is there workflow automation that reacts to a payment failing: Clerk will tell you the charge failed, and what happens next is still yours to build. Those stay separate purchases. A dedicated metering engine like Lago covers that specific gap in more depth than a bundled module does - see how Lago's metering compares to ours if that's the piece missing from a Clerk-plus-Stripe stack.
Pricing, and what we could not check on 16 September 2026
This section used to quote six Clerk prices. They are gone, and that is deliberate.
Clerk's pricing page would not load for us when we re-checked on 16 September 2026. We could reach Clerk's documentation but not the page the numbers live on, so we cut the figures rather than move the verification date and hope. A competitor price you cannot check is worth less than no price at all, and there is a specific reason to distrust the old ones: the parts of Clerk's billing we could read have visibly moved since August.
Here is the model, from Clerk's own docs on 16 September 2026.
Clerk bills per user, in Monthly Retained Users. An MRU is a user who comes back at least one day after signing up, so a signup that never returns does not bill. That free day is a thoughtful piece of design and we would happily copy it.
The B2B side is what changed. Clerk now meters organizations separately as Monthly Retained Organizations: an organization with at least two members, one of whom is an MRU. Free plans include up to 50 MROs in development and 100 in production. What this post called the "organizations add-on" is now the B2B Authentication add-on, and it reaches further than a rename suggests - it gates linking enterprise connections to organizations, self-serve SSO, and any seat limit above 20 seats.
So a B2B bill on Clerk is a paid plan, Pro or Business, plus that add-on. Two lines, not one. Enterprise connections themselves are free in development and capped at 25 there; in production the docs say the plan covers them and point at the pricing page for the rest. Read Clerk's pricing page for the numbers, and treat any Clerk price you find quoted elsewhere, including in this post's history, as needing a fresh look.
BuildBase's model is flat per-plan - Launch at $49 a month, Grow at $99 - with no free tier, though the 7-day trial does not ask for a card. Current numbers live at /pricing. For what the wider stack costs once Clerk's own billing is not enough by itself, see the real monthly cost of Clerk plus Stripe plus Lago plus Knock.
One more thing the docs are clear about, and it is easy to miss when you are comparing headline rates. Clerk Billing is USD only, does not support refunds, and does not support payment methods that need a 3D Secure challenge, which means those payments simply fail. It is unavailable in Brazil, India, Malaysia, Mexico, Singapore and Thailand. And there is no native mobile checkout: web and Expo web only, with no Apple In-App Purchase or Google Play Billing. If you sell into any of that, the price was never the deciding factor.
| Feature | BuildBase | Clerk |
|---|---|---|
| Free tier | No free plan, 7-day trial | Free plan, allowance on their pricing page |
| Entry paid plan | $49/mo (Launch) | Pro, then Business (prices not verified) |
| Billing unit | Flat per plan | Monthly retained users, plus organizations |
| B2B organizations | Included | B2B Authentication add-on, metered as MROs |
| Enterprise SSO / SAML | Not available | SAML and OIDC, production requires a paid plan |
| Framework support | Next.js, Vite, React Router / Remix, TanStack Start, Express, NestJS, Fastify, Hono, Astro | Next.js, React, Vue, Nuxt, Expo/React Native, and more |
| Scope | 20 modules, one instance | Auth plus its own billing objects |
Where Clerk wins
Two things Clerk does better today, and they are not small.
Enterprise SSO, and the gap is widening. Clerk ships SAML against Azure AD, Google Workspace, Okta Workforce or any custom SAML provider, plus OIDC including EASIE. We do not ship SAML at all. If an enterprise buyer has SSO on their security review, this comparison is already over and Clerk wins it.
Clerk also ships self-serve SSO, which this post did not mention in August: your customer's own IT admin claims a domain with a DNS record, picks an identity provider and tests the connection themselves, from a Security tab inside the organization profile. That removes the part of an enterprise deal where someone on your side hand-configures a connection per customer, and it is not a gap we are quietly closing. We ship nothing like it.
Framework reach. Clerk supports Vue and Expo/React Native alongside the usual web frameworks. Our list is Next.js, Vite, React Router / Remix, TanStack Start, Express, NestJS, Fastify, Hono and Astro - narrower by design. If your frontend is Vue, or your app ships as a mobile client, Clerk covers ground we do not.
How to actually decide
Write down what your next twelve months actually require, not what would be nice to have. If the list is "auth, and maybe an enterprise SSO deal," Clerk is the right tool, and its dedicated focus on auth shows in the product. If the list runs to workspaces, metered billing, workflow automation and RBAC that all need to agree with each other, you are choosing between one instance and the several vendors Clerk still leaves you to wire together. Kinde vs BuildBase is the same shape of decision if Kinde is also on your shortlist, and if a one-time boilerplate is on it instead, the accounts you still operate after paying once is the other axis of the same question. If you are not writing a codebase at all - if the product is a Webflow or Squarespace site - the comparison that actually applies is Outseta vs BuildBase, not this one. And if Clerk itself isn't the fixed point - if WorkOS, Supabase or SuperTokens are also on the list - Clerk alternatives breaks down which complaint each one actually answers.
We keep our numbers in one place at /pricing. Check Clerk's own pricing page before you commit, and do it yourself rather than trusting a number in a comparison post, including this one. Theirs moved this year with the shift to retained-user billing, it has moved again since August, and on the day we went looking we could not load it at all.