What is entitlement drift?
Entitlement drift is when purchased commercial state and observed product access no longer agree.
The problem name is entitlement drift. Find customers who did not receive what they purchased. Ropely does not decide what a customer should receive. It independently verifies that what was purchased is what the product delivered.
The comparison
- Purchased: invoices, subscriptions, store transactions, contracts, and provider entitlements you connect.
- Expected: the access those commercial facts imply after your mapping.
- Observed: what the application reported through access events.
- Drift: those layers disagree for the same subject in the same environment.
Shapes operators actually see
- Receives less: paid evidence exists, the product still shows free or locked.
- Receives more: access continues after cancel, refund, expiry, or a free plan.
- Pays twice: overlapping paid coverage that is not family sharing or an enterprise seat.
- Wrong subject: the paying identity is not the application user that received access.
What this page is not
Entitlement drift is not a billing-provider outage by itself, not a generic APM error rate, and not a request that Ropely become the live allow or deny service. Ropely watches the systems that already decide.