Billing
in a box.
Kribana is complete usage-based billing — built for your GTM team, not your engineering team. It replaces Stripe Billing, Chargebee, Orb, Lago and Metronome outright: no layer, no add-on, no homework.
Billing platforms ship homework.
AI turned pricing into a moving target — tokens, credits, hybrid plans, usage that swings by the hour. The billing market’s answer was API-first engines: Orb, Lago, Metronome hand your engineers the primitives and leave checkout, the portal, upgrade flows, entitlements and recovery for them to build. Six months of homework before you can bill, and a sprint every time GTM wants to change a price.
We’d already built the finished version. Kribana runs on proven technology from our prior product, Simplify, which ran checkout, renewals, upsells and metering in production. We know what complete looks like, because we’ve operated it.
So Kribana is the opposite of an engine: complete billing in a box, operated by the people who own revenue. Checkout, portal, pricing, wallets, entitlements and recovery — finished on day one, run from a dashboard by non-engineers, with a full API underneath when you want it.
Three things we won’t compromise.
If a customer has to build checkout, a portal, or dunning on top of us, we haven't shipped a product — we've shipped homework. Everything billing needs works on day one, on the processor you choose.
Pricing, packaging, experiments and recovery belong to the people who own revenue — operated from a dashboard, no tickets. The full API stays underneath for the day engineering wants it.
A dashboard that watches revenue leak is a spectator. Software that notices the moment and does something about it — that's the standard we build to.