No pages to build.
Checkout, plan changes, top-ups, payment methods, invoice history — your customers handle it all themselves from day one. Branded to you, hosted on your domain or embedded in your app.
Updated August 2026Self-serve billing, zero pages built.
Three steps. No engineering ticket.
Logo, colors and copy tone — dashboard settings, not a design project.
Point a subdomain at us for the hosted portal, or drop the embed into your app for a native feel.
Checkout, plan changes, top-ups and invoice history — handled without a support ticket.
One config, hosted or embedded.
Hosted and embedded aren't two separate products — they're two ways of surfacing the same underlying catalog and config. Point a subdomain at Kribana and customers get a fully managed, branded page; drop the embed into your own app instead and the same checkout, plan management and invoice history render natively inside your UI. Either way, you're maintaining one configuration, not two.
The portal doesn't have its own copy of your pricing that can drift out of date. When a new plan or price is published in the pricing engine, it shows up in the portal on the next page load — no separate content update, no redeploy, no CMS to keep in sync with the dashboard.
The self-serve scope covers what actually generates support tickets elsewhere: checkout for a new plan, upgrading or downgrading, adding a payment method, topping up a wallet, and pulling up past invoices. A customer can do all of it without emailing anyone, at any hour.
Branding — logo, color palette, copy tone — is a set of dashboard settings, not a frontend project. That's a deliberate trade-off: you get less pixel-level control than building your own portal from scratch, in exchange for a working, secure self-serve surface on day one instead of a multi-sprint build.
FAQ
What's the difference between the hosted and embedded portal?
The hosted portal is a fully managed page on a subdomain you point at Kribana — nothing to build or host yourself. The embedded portal drops the same checkout, plan management and invoice UI directly into your own app instead. Both read from the same catalog and configuration, so switching between them later doesn't mean rebuilding anything.
Does a pricing change require updating the portal separately?
No. The portal reads the live pricing catalog, so a change published in the pricing engine appears in the portal on the next page load, with nothing to redeploy or manually sync on your side.
Can customers download their past invoices themselves?
Yes — invoice history is part of the self-serve scope, alongside checkout, plan changes, payment methods and wallet top-ups. It's available to customers at any time without a support request.
How much can I customize how the portal looks?
Logo, color palette and copy tone are all dashboard settings, so you can match your brand without a frontend build. It's more limited than a fully custom-built portal, which is the trade-off for having a working, secure self-serve surface from day one.
Do I need engineering time to set up the portal?
No — pointing a subdomain at the hosted portal or dropping in the embed snippet is a configuration step, not a build project. There are no portal pages for your team to design or maintain.