However, we can proudly say that with nearly one million servers having passed through Cloudkick without being inadvertently rebooted, terminated, or otherwise... statistically, it's probably more likely that you'll accidentally terminate it yourself manually than that something untoward will happen to it if you're managing it with us. Our entire business is based on making server management better, easier, and safer for you and we do everything we can to make our service infallible.
In fact, some of the initial inspiration for our dashboard was that existing tools made it too easy to accidentally kill the wrong machines. Some providers give nodes names that aren't exactly user-friendly, and without some basic sorting and labeling tools, eventually almost anyone would make a mistake. So, we added coloring, sorting, and renaming to mitigate that kind of user error.
Also, on the subject of security, we just added the ability to require multi-factor authentication to log in to your Cloudkick account. You can choose to require a YubiKey, one-time SMS code, or one-time email code to access your dashboard. We did a brief write-up on our blog if you're interested in learning more: cloudkick.com/blog
I forgot to test one thing before terminating my trial (nice job by the way, the complexity is just a bit overwhelming initially): Is it possible to remove the API key once the initial setup is done as long as the agents are running on the monitored machines?
Here's the documentation: https://support.cloudkick.com/Agent/Cloudkick.conf
One thing of concern for me is that giving away my linode API key is not something I really would like to do. I don't use this key for anything at the moment, but my understanding is that it gives to the holder the right to delete my linode. not WANT. Arguably it's more a linode problem that it is cloudkick's