Subscription observability for AI apps
See when purchased allowance is not the granted balance. Ropely does not meter tokens or enforce access.
problem
AI products often sell credits or allowance packs in Stripe or RevenueCat, then grant those units in a separate ledger.
evidence
Commercial events prove purchased allowance. Access events or an allowance snapshot prove granted units. Ropely does not infer consumption, tokens, or model usage.
detection
When both sides exist, Ropely can show purchased allowance that exceeds granted units, and exhausted allowance that still has access.
impact
Impact is shown as integer-minor-unit revenue at risk in each currency separately. Currencies are never converted.
workflow
Connect a commercial source, add granted allowance with access events or a snapshot, then inspect the customer timeline.
integration
Typical sources include Stripe, RevenueCat, application access events, and an allowance snapshot. None of these is claimed as the only source.