# Stripe Billing vs BuildBase, and why it is not either-or

> Stripe Billing is the subscription engine on your Stripe account. BuildBase is the entitlement layer above it, on that same account. Here is what each one actually decides.

- Source: https://www.buildbase.app/compare/stripe-billing-vs-buildbase
- Section: Comparisons
- Author: Dharmendra Jagodana
- Published: 2026-11-05

## In short

Stripe Billing and BuildBase are not substitutes. BuildBase sells plans through Stripe Checkout on your own Stripe account, so Stripe charges for Billing either way. What differs is the layer above: Stripe Billing produces the invoice, BuildBase turns an active subscription into quotas and roles.

Most "X vs BuildBase" posts are about substitution. This one is not, and
pretending otherwise would cost you an afternoon.

BuildBase sells plans through Stripe Checkout on your own Stripe account. The
subscription it creates is a Stripe subscription, sitting in your Stripe
dashboard, raising Stripe invoices. So the question was never which of these
two charges your customer's card. Stripe does, either way. The question is what
sits above that charge and decides what the customer is now allowed to do.

## The one-paragraph answer

Pick Stripe Billing on its own if what you need is the invoice: recurring
plans, proration, tax, dunning and a customer portal you do not have to build.
Pick BuildBase if the invoice was never the hard part, and the work you keep
postponing is the code that turns "this subscription is active" into "this
workspace member may call this endpoint 40,000 more times this month." In
practice you run both, because BuildBase sells through Stripe either way.

## The fee is a constant, not a difference

Stripe charges 0.7% of billing volume for Billing, read from its own pricing
page on 4 November 2026. Its wording for what that covers is "Billing
transactions processed on and off Stripe," excluding one-off invoices. There is
a contracted alternative: $620 a month on a one-year contract for up to
$100,000 of monthly billing volume, then $1,500, $2,950 and $5,750 for the
$250,000, $500,000 and $1,000,000 tiers, with 0.67% above each cap. Card
processing sits outside all of that and does not change: 2.9% plus 30 cents for
domestic cards.

Now the part that decides this comparison. Because BuildBase's subscriptions
are Stripe subscriptions on your account, that percentage does not vanish when
you adopt BuildBase. Put it in both columns and move on.

TODO(dharmik): Stripe does not publish a per-integration-path breakdown of what
counts as Billing volume, so no public page settles whether a Checkout
subscription created through BuildBase is rated exactly like one created in the
Stripe dashboard. Confirm against a live account before anyone quotes a saving
here.

That is the opposite of what a comparison page is meant to say, which is why it
goes near the top instead of into a footnote. If you came looking for a way
around the 0.7%, the options that genuinely move that number are
merchant-of-record platforms and standalone metering engines, and they are
sorted by shape in [Stripe Billing
alternatives](/compare/stripe-billing-alternatives). We are not one of them.

## What each one actually decides

Stripe Billing decides what the customer owes. It models the plan, prorates a
mid-cycle change, applies tax, retries the failed card, and produces a document
a finance team can reconcile. That is a deep and unglamorous problem, and
Stripe has spent years on it.

BuildBase decides what the customer may do. A plan here carries entitlements:
features gated by plan, per-metric quotas, credits with a ledger behind them.
`bb.usage.record` meters a quota and checks it in the same call. The
subscription that defines that quota lives in the same instance as the
workspace it belongs to and the roles of the people inside it, which is the
agreement you would otherwise maintain by hand between three systems.

Does Stripe have entitlements? It has the primitives, and plenty of teams build
the layer themselves on subscription metadata. The real question is whether you
want to own that code, and how it behaves the week someone downgrades mid-cycle
while a seat is still active.

## The dogfood detail

Our own metering ends up back inside Stripe. PlugNode bills per flow run, and
on the paid plans workflow runs are a quota that bills over: $0.25 per 1,000 on
Launch, $0.15 on Grow, $0.10 on Scale. BuildBase counts those runs against the
workspace, then reports the overage into Stripe Billing Meters so the charge
lands on the same invoice as the plan.

If we thought Stripe Billing was the thing to replace, that is not how we would
have built it.

| Feature | BuildBase | Stripe Billing |
| --- | --- | --- |
| What it charges you for | A plan price that does not move with revenue | 0.7% of billing volume |
| Whose Stripe account | Yours | Yours |
| Invoices, tax and dunning | Stripe Tax and promotion codes at checkout | Its core product |
| Entitlements and quotas | Per-plan limits, credits ledger, quota checks | Build it on subscription metadata |
| Workspaces, roles and auth | Same instance, 20 modules | Not its job |

The price row is the one people read first. It is also the one most likely to
mislead, because a percentage and a plan price are not two quotes for the same
thing: they are two shapes of cost, and only one of them moves when you have a
good quarter.

## Our pricing, for the record

Ours comes out of the repo rather than off a web page. Free is $0, Launch is
$19 a month, Grow $49 and Scale $99, last checked against the production API on
31 October 2026. The paid plans open with a 7-day trial that does not ask for a
card. Free has no trial, because there is nothing to trial into. Live figures
are at [/pricing](/pricing).

Set that beside 0.7% and the shapes differ in a way worth noticing: a
percentage tracks your revenue, a plan price tracks your plan. [The crossover
math](/blog/billing-platform-revenue-tax) is worked properly elsewhere, with
one caveat for this page. That post compares a flat plan against a percentage
vendor you could drop. Stripe is not a vendor you drop.

> **Where Stripe Billing wins:**   **Invoicing depth we do not match.** Proration edge cases, credit notes, the
>   dunning retries Stripe tunes on its own data, and a customer portal that
>   handles the awkward cases without you shipping a screen. If your finance team
>   has opinions about reconciliation, those opinions are about Stripe Billing,
>   and they are reasonable ones.
>
> **It meters a long way for free.** Basic usage-based billing through the Meters
> API includes up to 100 million events a month. That is past the point where
> most products know whether their pricing model works at all.
>
> **Nothing to migrate.** Turning Billing on is a setting inside an account you
> already have. Adopting a bundle is a larger decision and a harder one to
> reverse, and it should be judged that way.
>
> **At small volume the percentage is cheap.** 0.7% of a few hundred dollars a
> month is a rounding error against any flat plan, ours included. Percentage
> pricing is genuinely kind to a product that has not found its revenue yet.

## Where each one is the wrong call

Stripe Billing alone is the wrong call if you keep writing the same
`if (plan === 'pro')` branch in new places and nobody can say what a trial
user is allowed to do without reading three files. That is an entitlement
problem wearing a billing costume, and no invoicing feature fixes it. The
shape of the fix is in [what entitlements
are](/blog/what-are-entitlements).

BuildBase is the wrong call if billing is the only thing you still need and
your auth, workspaces and roles already work. Adopting a backend to get quotas
is a bad trade when the rest of it would be replacing things that are fine. The
bundle pays off while you are still choosing the pieces, which is the same
argument [the Stigg comparison](/compare/buildbase-vs-stigg) reaches from the
entitlements side.

## If you are starting from Stripe Billing today

Stripe stays. You connect the account BuildBase will sell on, then define your
plans, prices and trials in BuildBase, and those sync out to that account. The
genuinely new work is the mapping from a plan to what it entitles, which is
also the thing you are actually adopting, so it is worth doing slowly.

TODO(dharmik): the repo documents the sync in one direction, plans defined in
BuildBase pushed to Stripe, and nothing I can find describes what happens to
subscriptions already running on that account when it is connected. Write that
path down before this post advises anyone mid-flight.

[How BYO-Stripe works](/blog/bring-your-own-stripe) covers the account side.
[Charging per API call](/guides/charge-per-api-call-nextjs) is the smallest
end-to-end example of the metering side.
