[heipei]

We just use a combination of numerical limits (e.g. API calls per day) and product flags as an array of tags (features:["module1", "module2"]). These limits and flags are attached set on "plans" which can be attached to accounts. Plans can be combined, in which case we'll take the larger value for each numerical value and combine the tags using union. Additionally one can override / add to any of these values on a per-account basis, so if your customer needs PlanX but a custom API quota then you just override that single value directly on their account.

Call me old-school, but I don't get why something like this should be outsourced to a third party.

[baq]

If you already have a process for repackaging entitlements in plans and addons whenever some bright mind in marketing has an idea, the it’s completely fine.

[jdwyah]

yeah, the overhead of another system for people to understand is non-trivial.

So your accounts can have N plans. Do each of those plans map directly to a sku that they are paying for?