Hi Roeme, thank you for your comment! >VisualOps is created with a goal of both "easy to understand" and "total control". We tried or best to associate the ea

Hi Roeme, thank you for your comment! >VisualOps is created with a goal of both "easy to understand" and "total control". We tried or best to associate the easy understanding to full control. I totally understand your point, and this is the idea behind VisualOps: you need to deal with complicated tools if you want to get total control (eg. Chef with OpsWorks), or you need to make some concessions if you want something easy (eg. PaaS platforms like Heroku). With VisualOps, you have a total control of your instances software configuration, as well as the "hardware"/"network" specifications available by AWS. >Complicated data format Even if someone hacked into our servers, took a copy of the data, stole our source code or laptop, they still cannot get your information. I think there is a confusion there. What we meant is that the AWS credentials are store on specific servers, which are not accessible by the employees here. These credentials aren't accessible using data stored on employees computers or internal git repos Thanks for telling us, we will modify this sentence, and sorry for the confusion.