12. REQUIREMENTS
• Non-leaky
• Blocked content does not appear in code
• Multiple providers
• Subscription fulfillment service, organization licenses, ULS-only accounts, etc.
• Portable
• Easy to implement on other sites
• Scalable
• Cached on WPVIP, Node.js-powered backend
• Respects subscription rules
• Active, inactive, unpaid, grace period, etc.
• Concurrency enforcement
• Limit on browser sessions, different limit for app users, different limit for organization licenses