Show HN: MadeiraCloud lets you draw AWS architecture and clone apps in minutes
madeiracloud.com
madeiracloud.com
Nobody in their right mind gives you their AWS-credentials just to get a glimpse at your product.
Edit: Any admin that gives these up should probably not be in the role they are. I'd fire someone over something like this. The OP commented further down that "64%" gave up their credentials. I think their bosses need to know about that or their clients should be warned.
I don't care who this guys is and how much assurance he can offer; there is no reason for this.
We definitely need to give more before users have to enter their credentials, like a tutorial and demo video which are in the works, but as far as actually using the product, I don't see a way around it.
As noted below, this is actually very common. RightScale, Scalr, OpDemand, NewVem, and all other AWS third party tools require this information.
Not trying to say you are wrong, you're not, it's rightfully a big concern for people, but unless AWS change the way their APIs work, what are we supposed to do?
RDS support is coming soon (approximately one month) and ELB support to be added shortly after that. AutoScaling and Availability Zones are both high priority, but we have very limited resources and I can't commit to a timeframe at the moment.
Thanks for creating IAM credentials and trying us out. If you have any suggestions on how to improved credential handling, please let me know.
I'm curious to see how well you guys get on asking for users to supply their AWS credentials. That used to be by far the most common feature request for S3stat, namely a way to use the thing without having to hand across your secret key.
I imagine you could allow your users to create IAM accounts with exactly the permissions they'd need for you to do your thing, but it seems like you pretty much need full control to be at all useful.
It certainly has been an issue, lots of requests and suggestions to make entering AWS credentials optional, but as you say, without the right permissions it would be useless.
Fortunately, it's the same for all third party tools which rely on APIs, no way around it, so a lot of users are used to having to give them out.
I'll share some stats from our small sample size so far: 63% of users who requested an invite then logged in, then of those users 64% entered their credentials, albeit with quite a bit of coaxing and reassurance.
When they realize how awesome it is they could upgrade to the plan thats monitors the cluster (and builds out larger clusters or provisions new ones).
Domain Name: madeiracloud.com Registered at http://www.dynadot.com
Registrant: INiT Inc. Peng Zhao HaiDianNanLu 12 Building 54, Room 110 Beijing, Beijing 100082 China
Administrative Contact: INiT Inc. Peng Zhao HaiDianNanLu 12 Building 54, Room 110 Beijing, Beijing 100082 China
+86 13911041736
Technical Contact: INiT Inc. Peng Zhao HaiDianNanLu 12 Building 54, Room 110 Beijing, Beijing 100082 China
+86 13911041736
Record expires on 2012/06/16 UTC Record created on 2011/06/16 UTC
Domain servers in listed order: ns1.dynadot.com ns2.dynadot.com
We don't try to hide the fact that we are based in Beijing (it is our location on our Twitter profile and there are several mentions of China in our blog) but we don't want to overly promote the fact either, for exactly this reason.
How does the knowledge that we are a Chinese company effect your decisions regarding our product? After finding this out did you go on to register and link with your AWS credentials?
Obviously, we can't help where we are located at this stage of the company, but I'd love to hear how you would recommend handling this from a business point of view.
I appreciate that the currently supported services does limit the scope of applications that our features could be useful for, but we felt that there are still a lot of people who can benefit from them right now and we wanted to get something out there early to get feedback. For sharing, for example, companies like http://labslice.com/ only support EC2 on its own.
Would you be able to share an indication of the take up you've had so far? Secondly, are you seeing users move from a free account to the premium, as they understand the possibilities available with the higher capacity for apps?
We launched our private beta in February and haven't done any paid marketing since then, all our users have been from word of mouth, media exposure and of course, the great HN. We 'launched' at an early stage and have been iterating since. Currently we have less than 700 free beta users and we are not offering the premium service yet until we have implemented our MVP feature-set and have ironed out any bugs our beta users report. I will be more than happy to share this information in the future.
I'll take it as a compliment, Heroku has a brilliant site and I hope ours can be as good but not appear to be anything close to a copy. It wasn't actually a reference during the design.
Do you have any suggestions on anything to change to make it less similar in your eyes?
Herkou is famous as being the first Rails PaaS to gain traction that was really "easy" to get started and push live.
This experience felt very similar - an impressive feit indeed, a similar feeling to what Herkou instilled the first time I saw their service.
The drag-and-drop web architecture super-easy-deployathon has that same slick awesome vibe (which is a good thing!), but coupling that with a similar layout, color scheme, and information architecture and its the first thing I jumped to.
Not a bad connection per se, but the original thought was "the guy that did the www site sweats herkou hard".
But seriously, thanks for this, I thought beyond the dark colour scheme and (very different shades of) purple there wasn't much more similarity. Next time I'm doing some redesigning I'll try and move it a bit further away.
Thanks for the compliments too.
The www site is a heavily customised theme built on top of Twitter Bootstrap 2.
The ide site is 100% hand made.