Thats a good point, right now we work solely off of API's and don't offer any way for us to store usersnames/passwords. The thought is that API credentials can be revoked easier. In general we are looking to meet the market of folks who are 100% in cloud environments, where the adoption of a SaaS solution is not as much of a concern. But in the future there are some ideas on how to handle self hosting and not sending credentials to the SaaS environment.

But we are open source, and our license does allow for self hosting: https://github.com/asm-products/cloudroutes-service/blob/mas...