Introduction
Seal0 answers one question: for this Customer, at this instant, which features and limits apply?
Your application asks Seal0 before it does something a plan controls: creating a project, enabling single sign-on, exporting a CSV, accepting another API call. Seal0 computes the answer from the Customer’s subscription, the plan version it’s pinned to, any overrides, and feature defaults, and says why.
{ "feature_key": "max_projects", "feature_type": "number", "granted": true, "value": 10, "source": "plan", "reason": "included_in_plan", "valid_until": null}What Seal0 isn’t
Section titled “What Seal0 isn’t”- Not authentication or authorization. It doesn’t know who your users are or what roles they have. Your code checks those, then asks Seal0 what the Customer’s plan allows.
- Not billing or payments. It never charges anyone. When your payment provider confirms a payment, your code assigns the subscription in Seal0.
- Not a feature-flag or experimentation tool. Entitlements come from commercial facts (plans, subscriptions, agreed exceptions), not rollout percentages.
The words Seal0 uses
Section titled “The words Seal0 uses”| Term | Meaning |
|---|---|
| Customer | An end customer of your product: a tenant, organization or user record. Seal0 knows it only by your own ID for it, such as cus_test_0001, and stores nothing else about it. |
| Feature | A capability or limit with a type: boolean, number, enum or metered. |
| Plan and plan version | A plan is a stable name, such as pro. Each published version is an immutable set of feature values. |
| Subscription | Assigns one Customer to one plan version, with lifecycle timestamps (trial, period, grace, cancellation). |
| Override | A different value of one feature for one Customer, for a time window. |
| Account, Member, Console | Your organization on Seal0, the people in it, and the web app where they manage plans and keys at console.seal0.app. |
| Project and environment | One application, with a development and a production environment that share nothing. |
How decisions are made
Section titled “How decisions are made”- Eligibility first. If the Customer has no subscription, or it is paused, expired, canceled, or past its trial, period or grace, nothing is granted.
- Then precedence: an active override, else the plan version’s value, else the feature’s default, else nothing.
- A missing entitlement is a normal answer,
200withgranted: falseand a reason, never an error.
Evaluation has the details. To try it, follow the quickstart.