I have used both. I would strongly suggest going with AWS.

Reasons:

Local development with Appengine is pretty bad. Good luck debugging and profiling production issues.

Appengine will make you jump through many hoops that undermine or completely drop pieces of the Django framework.

Getting data out of Appengine is a huge nightmare and timesink.

If you ever decide to migrate off Appengine you will need to rewrite almost everything.

This was my experience as well. I wish I had that month back.

I still have an app on GAE (the high availability version) mostly because I don't want to roll out my own HA Mongo DB. At some point it will become cost effective to do my own.

The other AWS plus: when my response time skyrockets, I can figure it out and fix it.

Was your data in the Appengine Datastore? I believe elicox was asking about using Google Cloud SQL, which I believe makes data export relatively easy (Cloud SQL is basically managed MySQL). New Django + Cloud SQL also runs basically "pure" Django, rather than the hacked-up djangoappengine of the past, so next to zero code should have to be changed in a move off AppEngine.

I recently made the switch from Datastore/djangoappengine to Cloud SQL, and it has been a far better experience.

Yeah I mean Cloud SQL, few years ago i was trying to replace the ORM of Django with he own AppEngine Datastore and it's a nightmare.

Want, got, had is a part of the concept of Mistash, my startup. http://www.mistash.com

It looks like Pinterest with relabeled buttons.

IMO it would have been better to create a unique name and then use "The agile planner" as the title attribute for your homepage.

Creating a unique name & domain would help you in the long run for search engines and brand recognition.

Searching for "the agile planner" on google has 1,950,000 results.

I've been working on my startup fulltime for close to 6 months now. I've been able to do it because of savings.

This was my noob submission to HN. I appreciate the helpful feedback on Mistash and have started to make some changes. I think next time I will have to post earlier in the day to HN to get more eyes. Thanks again everyone!

For staff we are using Google Apps. MailChimp for mailing lists. App testing uses Google Apps. App production (notification emails, etc) uses Amazon SES.

Agreed. I switched the tagline to the description from the about page.

Does seem that way lately. However, I do think Mistash has a better focus on the social aspects than the others and is also going in the best direction for a product focused system. Plus, it's more fun :P

Yup. For now, it combines a personal inventory, your wishlist , and various social features. The idea being that you can discover new products, share your tastes, and get higher quality reviews from the people you know.

I used to have a high fashion blog, and I would have probably found it valuable to curate my trending wishlists and to show off what I've bought and where from. It's kind of like a clever way of showing off what you own without bragging

My wife works in fashion, she thinks it could be a great way for models to share their wardrobe for photoshoots.

Heh, yeah. We've been struggling with a short tagline that will convey the concept clearly.