BTW. While AZ Controller community is a tiny subset of Sonar community, if someone has thoughts which DAW should be the next home for my project, may be we can have a success convincing corresponding developers. I do not need much from them, in fact they do not have to do nothing at all. All major players have Surface Integrations APIs which they use to support controllers, they just do not make these APIs public. There is a good reason, plug-ins like AZ Controller can damage/freeze/make unstable the DAW, including project corruptions. Not far away from the possible VST triggered damages, but still. Also, unlike VST, these APIs are dynamic, they change from version to version (Cakewalk has just stopped the development of its API long time ago, that is why all modern Sonar features can not be controlled).
With equal opportunity, accessible DAW will have my priority. While I know only one user for which that is relevant, one is not zero. I have made X3 accessible for him, with his plug-ins of choice and the controllers of choice. And I plan to do the same in case we switch to another DAW.
At the moment, the only DAW which fits is the Reaper. It has open API and accessibility binding. But as I wrote, the future of AZ Controller is not yet planed.