I have only just started with V10 (up from V8.8), but updates always include positive new features and V10 is no exception. The license model works well for me as I am in the process of rehosting my server, which includes moving to V10 on my development, staging, and production systems (staging and production are on AWS). I’ve already turned licenses on and off to meet certain needs. Note that after deactivating a license, you have to restart your control panel (or reboot the services) to fully deactivate the license. As for developing/testing on the production system, that’s been a hard no for me since I started with AwareIM in 2008. It’s a good concept but if you have a serious production system, you must have a way of testing the platform changes before going live. For example, Kendo and Jasper changes have often caused problems. Hence, at least a development license and production license for most situations. The point made above about putting the system into a do-loop in testing is one of many supporting points. I have used the migration tool for test data, and it works well but my production data is simply too large for that process (I use volume snapshots on AWS for backups and data relocation). I’m glad the config tool windows adhere to normal sizing better, but my focus has been rehosting without digging into development activities. As a general rule, I say resistance is futile and as developers, we have to stay current on our platforms. In my former professional life, I witnessed many large-scale system implementations in serious pain for not modernizing when they had the chance making the path forward far more painful and costly. I’ve experienced some of that myself.