Skip to main content

​
The authorization layer for monetized software

Your pricing changes. Your customers change. Your product shouldn’t have to. Kerne keeps the rules between what a customer bought and what your application lets them do out of your code.

​
The problem

Every commercial decision eventually lands in a source file:
Each of those is a business rule written somewhere you have to redeploy to change. And there is never just one of them — they spread across services, drift apart, and quietly disagree.

​
What Kerne does

Everything that should change what a customer can do goes in one side. One answer comes out the other.
Your application asks one question, and never learns why the answer is what it is:

​
What Kerne handles

Change your offers

Publish a new version of what you sell without silently changing the terms of customers who already bought the old one.

Control access

Turn what a customer is entitled to into a decision your application can enforce on every request.

Handle usage

Measure something once, then use it for an allowance, a hard stop, or a charge for the excess.

Handle exceptions

Give one customer different limits or access without inventing a plan for them or touching your catalog.

​
How it works

1

Define what you sell

Create your offers and what each one includes, in the dashboard.
2

A customer gets a version

Their access is tied to the terms they actually received — not to whatever your catalog says today.
3

Your application asks Kerne

4

Kerne makes the decision

Your application doesn’t need to know whether that access came from a plan, an allowance already spent, a negotiated exception, a failed payment, or a version of your offer you stopped selling two years ago.That’s the abstraction worth having.

​
Where the money moves

Kerne is not a payment processor. Stripe still moves the money, holds the card details, and handles the legal side of billing. The split is clean: your provider is told what to charge, Kerne decides what that entitles someone to. Your own code never names a plan, a price, or a provider.

​
Start here

Get started in minutes

Model your offers, connect your code, connect your billing provider.

Your first access decision

Create an offer, check access, then change the offer.

How Kerne works

What Kerne holds, and how a decision resolves.

Design your pricing

Bundling, metering, and add-ons.