[cparedes]

So, tell me - what would this tool offer over, say, RunDeck or mcollective? Why only use SSH keys? (What if I'm using LDAP across all of my machines?)

I'm not trying to knock your product - I really do hope you get Kickstarter funding! But I just wanted to say that, to me, as a systems engineer, I only see a pretty interface, but not much value add over the other two products mentioned above

I also feel that comparing Commando.io to Puppet, Chef, or even Capistrano is disingenuous - Puppet and Chef are configuration management systems that are meant to keep your systems 'in policy', and Capistrano is meant for repeated tasks over SSH (mainly for deploying software, but it can be used for other things too.)

[nodesocket]

(Creator of Commando.io here) - Thanks for the feedback. Commando.io is very young, and while currently only supports SSH, LDAP could easily be added. The alpha build is extremely minimal, and serves as a proof of concept. However future features are parellel execution, interactive sessions, scp transfers (maybe even Murder transfers [bitTorrent]), and provisioning.

You have to think back, when GitHub first launched, they probably had a minimal product. It takes a bit iteration to add the "eureka" features.

[benjamincburns]

I applaud what you're trying to do, but I think you hit the nail on the head in your last sentence. You need more iteration in order to find something that sets you apart. I wouldn't contribute to this kickstarter because I don't see anything here that really differentiates you from your competition in a way that would make people want to pay for your service.

If you missed Alex Loddengaard's "One Year, Six Products," you might want to check it out. http://alexlod.com/2012/07/10/one-year-six-products-what-ive...

[cparedes]

You can use LDAP logins and passwords with SSH by using pam_ldap - but since you only allow SSH keys, it'll be a non-starter for many orgs to use your product.

Best of luck - I'll keep an eye on it for sure.