Entitlements

Entitlements are the rules that map a customer's plan or purchase to the specific features, limits, and access they're allowed — the system that answers 'can this user do this right now?' For example, a Pro plan might grant 10 team seats, 50,000 API calls a month, SSO, and advanced analytics, while Free grants none of those. Entitlements are the enforcement layer that sits between your billing engine and your product. Why it matters: hard-coding plan checks (`if plan == 'pro'`) scattered through your codebase becomes unmaintainable the moment you add a tier, run a promo, or grandfather a customer. A clean entitlements layer lets you change pricing and packaging without redeploying, and enables per-customer overrides for sales-negotiated deals. Practical note: tools like Stripe Entitlements, Schematic, or an in-house table keyed on tenant let you decouple 'what they pay' from 'what they can access.' Model entitlements as data, not code, so non-engineers can adjust packaging safely.