Thanks for the questions! So I'm currently working on making both the licensing and distribution APIs support whitelabeling via a CNAME DNS record, but at the m

Thanks for the questions! So I'm currently working on making both the licensing and distribution APIs support whitelabeling via a CNAME DNS record, but at the moment, no, it's not supported. You can set up a proxy server in front of either API with your own domain (similar to how you would integrate e.g. AWS S3 behind your own domain using their API), but that's about it for now. And for your other questions: 1) I'm not sure I'm understanding you 100%, sorry. But it seems like you're asking about pricing changes for Keygen itself? I don't plan on hiking up prices on customers without due notice (even then, all past pricing changes have grandfathered in current customers' plans), and if they decided to part ways with Keygen because of a pricing change (e.g., maybe their volume doubled and I ask them to upgrade to a larger plan to support the additional traffic) I'd be more than happy to help them with a transition plan so that their customers don't suffer, but that would of course be on a case-by-case basis. Is that what you meant? 2) No, I don't think I would have an issue with a vendor mocking my API endpoints to make sure their software continues to function. Better yet, they could purchase an on-premise install and run the APIs themselves via Docker, and even purchase an additional license to modify the on-premise server's code to meet their needs. Vendor lock-in sucks, so thanks for asking these questions. I'd be happy to hear suggestions you may have on how I could better deal with the vendor lock-in fears a lot of companies seem to have when integrating third-party APIs (understandably so).