Having a product that also involves connecting to other people's databases we're pretty well versed in this problem. I will admit its a bold step to allow an ex

Having a product that also involves connecting to other people's databases we're pretty well versed in this problem. I will admit its a bold step to allow an external service access to your production databases but as a trade off of convenience vs security the former does win more often then people would think. This is especially true for people using PaaS/DBaaS providers which by default allow access from all inbound IPs (ie not white listed). One thing we try to do is be open about all this and we explicitly mention it in our docs[1]. This includes instructing users to explicitly limit the permissions that they grant. Another poster mentions loading a pre built VM. thats actually our goal for the enterprise as there will always be systems are not (and should not!) be accessible to the open Internet. In the meantime though there plenty of folks happy with the convenience of living in the cloud. [1]: http://www.jackdb.com/docs/#security http://www.jackdb.com/docs/#security