Base316
Billing, entitlements and authentication for products that charge by usage.
Base316 answers one question on the request path of your application:
May this account do this, and who is billed for it?
It holds your plans, what each one entitles an account to, how much they have used, and what they owe. Your code asks; Base316 decides.
Two halves that share one model
Billing — plans, subscriptions, usage metering, invoices, proration, discounts, credit notes and dunning. Money is collected through Stripe Connect, where your customer stays the merchant of record.
Identity — your application's own users, organisations, roles and permissions, with hosted sign-in, SSO, OIDC and SAML for the accounts that demand it.
They share a model on purpose. A permission check and an entitlement check are the same question asked about different things, and answering them separately is how an application ends up entitling a user its billing system thinks left three months ago.
Start here
Quickstart
A key, a first call, and a gated feature — in about fifteen minutes.
How the model fits together
Environments, customers, plans, features. Read this before designing your catalog.
Gate a feature
The call you will make most often.
Coming from Chargebee?
Import customers and subscriptions without billing anybody twice.
What it is not
Base316 is not a payments company. Charges are created directly on your own Stripe account, you keep your Stripe dashboard, and a chargeback settles against your balance rather than ours.
It is also not a data warehouse. Usage events are metered and rated; they are not a general event store, and Base316 will not answer analytics questions about them.