It sounds like Keygen considers a "subscription" and a "license' to be a 1-to-1 relationship, correct? Most billing/subscription managers I've looked into support the concept of a subscription that supports multiple seats/licenses. To model this in Keygen, the subscription would map to the license and the number of allowed licenses on the subscription would map to the "machines" allowed to use the license, correct? License == Subscription. Machine == Licensed User ID?
While this could work as a quick go-to-market solution I think ideally it would be a many-to-1 relationship between the license (seat) and the subscription. We also want to support the "machine" concept too where we wouldn't want an individual user license to be abused by being concurrently used on multiple devices beyond what an individual user account should be doing (i.e. allow X signed in devices per user).
> You can hide the license from your customer by storing the license identifiers in your CIAM's user metadata, and then hitting Keygen's API after the user has authenticated and you're able to read those metadata values. E.g. storing the license ID, key and the license's API token is typical.
Curious about the distinction between these attributes. Maybe you can educate me: what's the difference between the license ID and license key? And does the API token restrict client access to just that licenses' information? We definitely would be validating licenses from a client/mobile app and not having app level API keys in the mobile client is certainly desirable.
> Being able to offer a customer-facing portal is one of my priorities in 2022, so I will eventually offer this out-of-the-box.
I can see this as being a tall order to get right in the general market sense. Which I'm sure is why few (none?) out-of-box solutions exist. Being able to white label this product will be important. Also supporting the CIAM of your customer so they can be the identity provider/authentication source for their own customers so separate sign in to manage separate accounts/services isn't necessary. Allowing management/license assignment of multiple products with multiple subscriptions etc.. Allowing designation of admin like roles/permissions within the same CIAM directory of your customer securely -- I can see how this can all get hairy real fast. But if you can get it right I can see a market for this.