# Orb vs BuildBase: what $6.00 a credit actually buys

> Orb now publishes a self-serve price: $6.00 per credit, with credits drawn by billings and by ingested events at the same time. Here is the arithmetic, and where BuildBase fits instead.

- Source: https://www.buildbase.app/compare/orb-vs-buildbase
- Section: Comparisons
- Author: Dharmendra Jagodana
- Published: 2026-11-06

## In short

Orb charges $6.00 per credit on its self-serve Business plan, and credits drain from two meters at once: one per $1,000 of billings, one per 200,000 ingested events. Past 200 events per dollar billed, ingestion sets your bill rather than the 0.60%. BuildBase makes billing one of 20 modules on your own Stripe account.

For years the honest answer to "what does Orb cost" was that nobody outside
their sales calls knew. The roundups on page one still say contact sales.

That changed. Orb publishes a self-serve price now, and the pages telling you it
does not are out of date. The price turns out to be stranger than a percentage.
None of them has done the arithmetic on it, so we did.

## The one-paragraph answer

Orb is a dedicated usage-metering and billing engine, owned by Adyen since July.
Its Business plan costs $6.00 per credit, and credits drain from two meters at
once: one per $1,000 of billings processed, one per 200,000 events ingested. BuildBase is an
SDK where billing is one of 20 modules, sitting beside authentication,
workspaces and role permissions, and running on your own Stripe account. Pick
Orb when metered events genuinely are your pricing and getting them right is an
engineering problem. Pick BuildBase when billing is the fourth system you have
not built yet. They barely compete, because they answer different questions.

## What a credit actually is

A credit is two meters sharing one balance. Orb's pricing page quotes the rate:
$6.00 per credit on Business, or less with volume discounts, and new accounts
get 100 free credits. An equivalence sits in the FAQ: one credit "works out to
0.60% of billing volume, plus event ingestion and other metered dimensions."

Read that second clause again. It is doing more work than it looks.

The consumption table underneath tells you what a credit really buys, and it is
not one thing. One credit is $1,000 of billings processed through Orb. It is
also 200,000 events ingested, live and test alike, and two credits is 500,000
rows exported. Those are not
three ways of describing one credit, they are separate meters drawing down a
single balance.

So your bill is not 0.60% of revenue. It is that **plus** $0.03 per 1,000
ingested events, which is what $6.00 per 200,000 events works out to, and the
0.60% is simply the floor you pay when you ingest almost nothing.

## The crossover is 200 events per dollar

The ingestion dial starts costing more than the billings dial at **200 ingested
events per dollar of billings**.

The arithmetic is short. Billings consume credits at one per $1,000, so a dollar
of revenue burns 0.001 credits. Events consume credits at one per 200,000, so an
event burns 0.000005 credits. Divide one by the other and the crossover falls at
200 ingested events for every dollar of billings. Below that, revenue sets your
bill. Above it, your meter does.

Two products, same revenue:

A B2B tool bills $50,000 a month and ingests two million events. Billings cost
50 credits, events cost 10 credits, so 60 credits at $6.00 is $360. That is
0.72% of billings, a fifth above the headline and no real surprise.

An AI product bills the same $50,000 and ingests twenty million events, because
it meters per call and per token. Billings still cost 50 credits. Events now
cost 100 credits. The bill is 150 credits, or $900, which is 1.8% of billings -
three times the number on the pricing page, for identical revenue.

Neither product is being overcharged. Orb's costs really do scale with ingestion,
and pricing the thing that drives your cost is defensible. But a founder who
budgets 0.60% off the FAQ and happens to be building the second product will be
wrong by a factor of three, and no page currently ranking for Orb's pricing will
have warned them.

Work out your own ratio before you model anything. Monthly ingested events
divided by monthly dollars billed. If that number is comfortably under 200, the
headline percentage is roughly your bill. If it is over, ingestion is what you
are buying. Price it as such.

## Where BuildBase charges differently

BuildBase charges a flat plan price and takes no share of your revenue. Free at
$0, then Launch at $19, Grow at $49 and Scale at $99 a month, with a seven-day
trial on the paid plans and no card needed to start one. Yearly is ten months
for twelve. Those were current on 31 October 2026, and the live ones are always
at [/pricing](/pricing).

Nothing in that scales with what you bill your customers. Stripe's own fees are
Stripe's, charged to [your own Stripe account](/blog/bring-your-own-stripe), and
nothing sits in between. We do meter three things and bill overage on them:
workflow runs at $0.25, $0.15 and $0.10 per 1,000 on Launch, Grow and Scale, web
analytics events at $2 per 100,000, and storage at $0.10 per GB-month. Every
other quota is a hard allowance that simply stops.

That is a deliberately smaller promise than Orb's. Our billing module does plan
versioning, seat and usage pricing in flat, graduated or volume tiers, add-ons,
promotion codes, Stripe Tax, and a credit ledger with expiry and auto top-up.
Per-plan limits apply to any metric you define, with overage reported to Stripe
Billing Meters. What it is not is an ingestion pipeline.

| Feature | BuildBase | Orb |
| --- | --- | --- |
| Published price | Free $0, then $19, $49 and $99 a month | Business at $6.00 per credit, less with volume discounts; Enterprise is custom |
| How the bill grows | Flat plan price; overage only on workflow runs, analytics events and storage | Credits drawn by billings ($1,000 each) and events (200,000 each), so revenue and ingestion both push it up |
| Event ingestion | Per-plan limits on any metric, with overage reported to Stripe Billing Meters | Hosted rollups documented at 1M+ billing events per second in production |
| Late data and corrections | Not built | Backfills that recalculate affected invoices, and simulations against historical usage |
| Revenue recognition and ERP | Not built: no revenue recognition, no accounting sync | Recognized and deferred revenue with exports, plus a one-way NetSuite sync |
| Auth, workspaces and roles | 16 sign-in methods, multi-tenant workspaces and role permissions in the same instance | Out of scope: Orb is a billing and metering product |
| Payment relationship | Your own Stripe account | Owned by Adyen since 1 July 2026 |

## The acquisition, with less certainty than you have read elsewhere

Adyen acquired Orb. Its own knowledge hub says the deal was announced in June
2026 and completed on 1 July. That much is from the acquirer and is solid.

Beyond it, be careful. A deal value circulates widely in third-party coverage,
and so does a description of how Adyen runs Orb internally, but neither appears
on an Adyen or Orb page we could load today. We have repeated both in [our own
earlier writing](/compare/lago-alternatives), and on this pass we could not
stand them up, so they are not in this post. Treat any specific number you see
attached to this deal as reported rather than confirmed.

What the acquisition does change is the premise of every "neutral metering
engine" pitch. [Metronome went to
Stripe](/compare/metronome-vs-buildbase) on 14 January 2026, per Stripe's own
newsroom post, and Orb went to Adyen on 1 July. If you
were shopping for a metering layer precisely so a payments company would not own
it, the two deepest options on the list are now owned by payments companies. That
may not matter to you at all, and Orb's engine did not get worse on 1 July.

## Where Orb wins

> **Where Orb wins:** Three things, and they are not close.
>
> **Throughput we do not publish a number for.** Orb documents hosted rollups
> handling 1M+ billing events per second in production deployments. Our constants
> carry no throughput figure at all, deliberately, because our metering is sized
> for per-plan quotas and overage rather than for being the pipeline behind
> someone's inference API. Orb's own customer page names Vercel, Replit, Supabase
> and Baseten, which tells you the volume band it is built for.
>
> **Late data, and being able to change your mind.** Orb ships backfills and
> corrections that recalculate already-issued invoices when events arrive late,
> and simulations that replay a pricing change against historical usage before you
> ship it. BuildBase has neither. If an event lands two days after the invoice, we
> have no story for that and Orb has a product for it.
>
> **The finance side of billing.** Orb tracks recognized and deferred revenue with
> exports, and syncs to NetSuite as real invoices, credit memos and customer
> deposits with line-level service periods. BuildBase ships no ERP integration, no
> accounting sync and no revenue recognition in any of its 20 modules. A finance
> team closing the books in NetSuite is a customer we do not serve, and no amount
> of module count changes that.

## So which problem do you have

Ask what breaks first, not which is cheaper.

If events are the product and double-counting one is a revenue incident, you
want metering infrastructure, and you should go read the field properly rather
than take our word for it. [The best usage-based billing
tools](/compare/best-usage-based-billing-tools) and [metered billing for AI
products](/compare/best-metered-billing-tools-for-ai-products) both cover Orb,
and it comes out well in both. [Lago](/compare/lago-vs-buildbase) is the one to
look at if self-hosting matters.

If instead the honest description is "we bill a few hundred companies for seats
and a plan tier, and we also need login, and workspaces, and a way to say who
can see what", then a credit that drains on ingestion is priced for a problem
you do not have. [Metered and seat-based billing are different
businesses](/blog/metered-vs-seat-based-billing). We costed the multi-vendor
version of that stack in [the real monthly cost of Clerk plus Stripe plus Lago
plus Knock](/blog/auth-billing-stack-cost), and the integration work between them
is the line item that never appears on anyone's pricing page.

We know the second shape because it is ours. BuildBase meters its own workflow
runs through the same module we sell, which is how those overage rates above
exist at all, and PlugNode runs usage-based credit metering on it. The thing that made
that work was never ingestion throughput. It was that the meter already knew
which workspace a run belonged to and whether the caller's role was allowed to
start it. Bolt a metering engine on from outside and those two questions are
yours to answer, in glue code, for every product you ship. That is the trade. We
give up depth, and the three things above are not a courtesy.

A note on sourcing. Orb's $6.00 per credit, the 100 free credits, the 0.60% FAQ
line and the consumption table (one credit per $1,000 of billings and per
200,000 events, two credits per 500,000 exported rows) were read on withorb.com
on 6 November 2026, as were the page-one search results described at the top.
The hosted-rollup throughput, backfills, simulations and revenue recognition
come from docs.withorb.com the same day, the NetSuite behaviour from Orb's own
product page, and the customer names from its customers page. Orb's acquisition
dates are Adyen's own knowledge hub, and Metronome's are Stripe's newsroom, both
read the same day. Every credit calculation above is ours,
worked from Orb's published figures and shown so you can check it. Our plan
prices and overage rates come from the shared constants this site builds from,
verified 31 October 2026, and the live ones are always at [/pricing](/pricing).
