A monthly active user is the advertised unit, with no number attached

Braze’s four editions, Go, Select, Pro and Enterprise, are all billed on monthly active users, yet none of them publishes an amount, a currency, a threshold, or a commitment length. The only quote-free way in is a thirty-day free trial.

SMS is billed in credits, kept apart from email and push

Once inside a plan, Braze doses SMS, MMS and RCS in “by segments” credits, a unit kept distinct from email, billed as “total email sent,” and from push, metered on its own again. No list of covered countries accompanies that credit meter.

A third unit surfaces only inside the API documentation: data points

Braze’s published API limits carve out a burst allowance of three thousand requests every three seconds specifically for “data-point-billed customers” — a billing unit that never appears on the pricing page itself, only inside the developer reference for a completely different resource.

Braze publishes all three units and reconciles none

Monthly active users, per-channel credits, and data points are three separate meters running under the same subscription, and Braze’s own pages never convert one into another or state which one ultimately sets the size of the bill. A buyer is left to ask a customer success manager how the three connect, because the public pages simply do not say.

Klaviyo starts free, and the free line is the only one that can be checked

Klaviyo’s only verifiable price is its free plan, at zero dollars a month, capped at two hundred fifty profiles and five hundred emails, with Klaviyo’s own branding forced into the footer. Every paid tier above it renders in JavaScript on the pricing page, so no comparable figure can be read there at all.

What moves the Klaviyo bill, against what moves the Braze bill

Klaviyo’s tier depends on active profiles and emails sent inside the billing cycle, and a flexible overage bills the entire next tier at once rather than metering the actual usage. Braze’s own hidden costs run on a different axis: catalog storage past five hundred megabytes, a Currents data feed granted only on request, and API limits that a customer success manager can raise by hand, with any renewal increase capped at seven percent either way.