What each plan unlocks v4
StarterGrowthScale
sso.saml ––On
audit.export –OnOn
seats.active 52580
api.requests 0.5M2M4M
One packaging record, read on every surface
Plans decide what customers can do.
Map features and limits to plans, then enforce them through one API.
The check
Evaluated against
The answer
POST /v1/entitlements/check Your product asks before it acts.
{ customer "cus_8f21d4" feature "audit.export" quantity 1 entity "eu_1" }
No cache, the live plan answers
asks
SC Scale v4 The record that prices the plan
audit.export Included in Scale On
Quota on the feature No ceiling on this plan None
Catalog version Held until you migrate v4
One catalog, price and access
9 ms
Allowed 200 OK Included in Scale, with no quota set on the feature.
{ allowed true reason "in_plan" remaining null plan "scale_v4" }
Already in plan, nothing to buy
Quotas on this account
seats.active 78% 62 of 80
api.requests 48% 1.9M of 4M
storage.gb 32% 640 of 2,000
webhooks.endpoints 36% 9 of 25
Plans decide access, everywhere.
Map features and limits to plans in the catalog, then enforce them anywhere through a single API.
Book a demo-
Feature entitlements
Turn a feature on or off by plan, in the catalog rather than in the code. Your product asks what the plan unlocks and gets the same answer everywhere.
-
Metered limits
Quotas per plan on seats, calls, storage or anything else you meter. Every check is answered against the customer’s current subscription, in real time.
-
Overage rules
Decide per limit what happens at the ceiling: block the action, meter it for later, or charge for it. The rule lives on the plan, not in your app.
-
Real-time API
One call asks whether a customer may do something and how much of a limit is left. The answer comes from the live subscription, not a nightly export.
-
Grandfathering
A customer keeps the entitlements of the plan version they bought until you migrate them. Publishing a new version changes nothing for them.
-
Tied to the catalog
Entitlements are part of the price book, so packaging is the same in every currency and entity. One change to a plan reaches every account on it.
Gate features without shipping code.
Package by plan
Define what each plan includes in the catalog. Your product reads entitlements from Occurly, so changing what a plan unlocks is a config change, not a release.
- Feature flags driven by plan
- No deploy to change access
- Consistent across surfaces
Quotas your product can trust.
Enforce limits
Check limits in real time and decide whether to block, meter or charge overages, so usage caps are enforced the same way everywhere.
- Real-time limit checks
- Block, meter or charge overage
- Live remaining-quota lookups
Works with the rest of Occurly.
Eleven modules on one data model, one catalog and one ledger.
Entitlements
questions.
How does my app check entitlements?
Call the entitlements API to ask whether a customer has a feature or how much of a limit they have left. Occurly answers in real time from the current subscription and catalog.
Can limits and overages be enforced?
Yes. Define usage limits and quotas per plan, and choose to block, meter or charge overages when customers exceed them.
What about customers on old plans?
Grandfathering is built in. Customers keep the entitlements of the plan version they are on until you migrate them.
Let pricing drive product access.
Book a demo- 30 minutes
- A working session on your packaging, not a slide deck.
- Your plans
- We map one of your real plans to entitlements, live.
- In writing
- Scope, migration path and commercials follow the same day.