SaaS subscriptions
Ship paid plans without rebuilding subscription state, entitlement checks and billing edge cases in every protected surface.
Licenzy handles subscriptions, AI credits, usage packs, and access control on top of Stripe.
Start free in test mode. Upgrade only when you go live.
/v1/access/check{
"subject_ref": "user_123",
"feature": "ai.generate",
"allowed": true
}POST /v1/access/checkPro plan access granted
POST /v1/usage/consume42 AI credits remaining
entitlement.activeRuntime state is ready
The pain is not charging a card. The pain is everything around it: webhooks, entitlements, access decisions, and billing edge cases leaking into product code.
Stripe handles payments. You still have to handle everything after the payment succeeds.
One integration surface instead of Stripe billing logic spread across services.
simplifiedLicenzy processes Stripe events and keeps entitlement state in sync.
stripe.invoice.paidinvoice.paidpro.activesyncedThe shortest path is simple: define what you sell, start checkout, let Licenzy grant entitlement, then check access in your product.
Step 1Products, AI credits, time passes, usage packs, and plans stay mapped to the runtime surface.
product.price.createduser_123ready: trueA simple access check says more than a generic SDK abstraction. This is the kind of request your backend actually makes.
const response = await fetch("https://api.licenzy.app/v1/access/check", {
method: "POST",
headers: {
Authorization: "Bearer lz_test_***",
"Content-Type": "application/json",
},
body: JSON.stringify({
subject_ref: "user_123",
}),
});
const result = await response.json();
if (!result.allowed) {
throw new Error("Access denied.");
}For teams that want billing in Stripe and product access logic in a cleaner runtime layer.
Run multiple apps or runtime workspaces under one account with isolated projects.
Ship paid plans without rebuilding subscription state, entitlement checks and billing edge cases in every protected surface.
Sell AI credits for generation limits, API usage and compute usage, then safely consume units after the real work completes.
Support developer products where checkout, access checks and customer entitlement state have to stay in sync.
Use the runtime API instead of rebuilding subscriptions, credits, access checks, and webhook handling yourself.
Need to talk through your setup first? Contact the team.