I doubt it is for free.
EDIT: they even get AWS's color palette right:
https://cdn-images-1.medium.com/max/1600/1*ypBcvVoRIWfirQTBq...
The person on the left.
https://cdn-images-1.medium.com/max/1600/1*YrtTkA-xV_eincZV6...
See the machine on the right, it resembles the yellowish color for AWS.
Our startup happened to get in on Appengine early on, and we went with it for exactly the reasons he puts forward. At the end of the day we spend all our time building our apps, instead of being diverted every time the mail server crashes, or a package needs a security upgrade, or our OS needs updating, or a hard drive dies, or a routing table gets corrupted, or replication fails between databases, or the load balancer is doing something strange. When any of those things does happen, I know the best sysadmins on the planet are jumping to fix it.
Having said that, there are a couple of provisos you need to bear in mind:
1. If you need to do anything outside the Appengine ecosystem (using unusual protocols or ports for instance), you're going to have to do it outside Appengine.
2. You have to write to Appengine's datastore. There are alternatives (MySQL for instance) but none of them give you automatic concurrency, scaling and redundancy. This is more painful, but it means if you ever hit the big time, you're covered.
I always imagined what would happen if Oprah mentioned our service on her show. If we had built on AWS (or Azure, GCS or other IaaS), I'd be tearing my hair out provisioning load balancers, web servers and sharding databases. With Appengine, all I'd need to provision would be a crate of champagne.
The article mentioned the Royal Wedding website. This was a great example of Appengine's strength, going from zero to thousands of hits a second and then back to zero. If you'd done it with AWS (or even worse, real hardware), imagine the difficulty of estimating the number of machines you'd need, and the cost of provisioning them. If you have a "bursty" service, Appengine just works and you pay for what you actually use.
And that's the other thing - what you pay is minimal. The Appengine user group is full of people complaining that it is more expensive than $CHEAP_HOSTING_PROVIDER, but as soon as you factor in any sysadmin time - or lost app development time - you come out ahead. We run three services with up to 2 million users, and the monthly cost is in two digits.
That’s like getting a turkey to vote for Christmas right? In fact IT is the department least accustomed to being automated. "We’re the guys who automate everyone else aren’t we? What’s this — now our own jobs are at risk? Woah." But it’s happening regardless and IT will resist it like all the other departments did. It’s human nature.
But the conclusion is... Unsettling, to say the least:
Enter the CFO who, in my recent experience, is the voice of reason. Now, more than ever, I see CFOs taking the lead in arbitrating technology decisions. This is the correct approach. IT must relearn the vocabulary of business: money.
Has a good CFO ever been a decisive factor in why a startup succeeds? I'm not saying they're not valuable, but if the CFO is making your technology decisions then it seems like you've already lost.
Every single infographic uses Google's color palette...
Oh, and I have just checked, and I really hate when people do this without a disclaimer: "3wks has been a Google Cloud Services Partner since 2012, building digital solutions for enterprise customers and public sector organisations specialising in web and mobile solutions on GCP."