118 engineers on Hacker News describe using Google Cloud Platform first-hand: 34 endorse it, 19 regret it, 7 are mixed.
“I use gemini in prod via google cloud. Why does a customer have to hear "Oh yeah, don't use Google Cloud now"”
mixed · production · hypendev · 2026-10-29 · source ↗ · wrong label?“We kind of like Google Platform for its flexibility, lowest cost, security and free offerings”
endorse · production · raxwan · 2026-10-24 · source ↗ · wrong label?“Nearly every failure required an engineer to manually intervene to get rid of the bad node, and then file a ticket with GCP support”
regret · production · 2 yr · claytonjy · 2026-07-23 · source ↗ · wrong label?“they turned quota on services I needed down to 0, refused to tell me why, and closed my appeal. I never figured out what went wrong.”
regret · production · leros · 2026-06-07 · source ↗ · wrong label?“I was forced to move away from the cloud primarily because of the high cost of running video processing”
regret · production · slroger · 2025-12-20 · source ↗ · wrong label?“some things in the Cloud come with default policies that are just absurdly limiting, which means you have to create a resource/account”
regret · personal · thecupisblue · 2025-12-11 · source ↗ · wrong label?“We can't get rid of Postgres, but since we run Postgres on GCP we really never even think about it.”
endorse · production · flanked-evergl · 2025-09-26 · source ↗ · wrong label?“we switched all of our CI fleet to the latest AMD generation C4D's and got 36% faster builds, but had to go back a generation because GCP kept running out of boxes for us.”
regret · production · reilly3000 · 2025-08-27 · source ↗ · wrong label?“Google Cloud support is an actual joke. I have no idea how to navigate their chatbot and speak to an actual human.”
regret · production · lomoeffect · 2025-05-29 · source ↗ · wrong label?“The number of APIs I have had to migrate over the past 5 years using GCP is shameful”
regret · production · 5 yr · warmedcookie · 2025-04-26 · source ↗ · wrong label?“As a Googler who works in GCP security, security has been a key differentiator for GCP long before the Mandiant acquisition.”
endorse · production · Thorrez · 2025-03-18 · source ↗ · wrong label?“the answer from google is something i will never forget. it was just "we don't offer support, sorry"”
regret · production · floydnoel · 2025-02-07 · source ↗ · wrong label?“I wrestled with GCP a month ago. Never again.”
regret · personal · more_corn · 2024-09-22 · source ↗ · wrong label?“we finally made a big effort and migrated all the object storage to GCP (which is faster and at a fifth of the price)”
endorse · production · tecleandor · 2023-12-07 · source ↗ · wrong label?“after dealing with GCP the last few months we abandoned our plans to port our model to JAX and decided to stick with GPUs for now.”
regret · production · leetharris · 2023-12-06 · source ↗ · wrong label?“We had our main GCP account suspended because we were running a Lightning node, and some Google automata flagged us as mining.”
regret · production · jb_gericke · 2023-10-26 · source ↗ · wrong label?“GCP has good support if you are big enough.”
endorse · production · sparc24 · 2023-10-11 · source ↗ · wrong label?“we moved to AWS after stability issues and horrendous support experience on GCP. GCP is a joke.”
regret · production · eknkc · 2022-09-29 · source ↗ · wrong label?“I run several million USD on GCP and it's fine.”
endorse · production · busterarm · 2022-09-24 · source ↗ · wrong label?“We had to stop/start instances exactly zero times, out of the thousands we run and have been running for years.”
endorse · production · outworlder · 2022-09-21 · source ↗ · wrong label?“We moved off Heroku about 2 years ago and use gcp. It's been really good.”
endorse · production · 2 yr · lostsoul8282 · 2022-05-04 · source ↗ · wrong label?“Google's offering shows an almost pathological disgust for their customers... They've had their chance and they've squandered it.”
regret · production · more_corn · 2022-05-02 · source ↗ · wrong label?“our dev cycles are much more streamlined now, it's rather easy to deploy an entirely new environment”
endorse · production · dijit · 2022-04-07 · source ↗ · wrong label?“We migrated ~80 microservices within 8 months and now our infra cost about 1/4 of what we paid to aws, completely worth the effort!”
endorse · production · pavelevst · 2022-04-07 · source ↗ · wrong label?“We moved to gcp got null routed (or reduced network bandwitch to the node under attack) every-time there was an attack.”
regret · production · malikNF · 2021-03-07 · source ↗ · wrong label?“we moved to google cloud specifically for GKE and it's been pretty great.”
endorse · production · jordanthoms · 2021-03-01 · source ↗ · wrong label?“Our GCP bill is about 1/3 of what AWS was”
endorse · production · cbushko · 2021-02-24 · source ↗ · wrong label?“I've been using serverless in both GCP and AWS for many years now and have helped migrate mid sized startups onto those platforms”
endorse · production · jamesappledev · 2020-12-20 · source ↗ · wrong label?“We use Google Cloud and Firebase at work and our application and servers are still up and running. Can't say the same about the Cloud Admin Console”
mixed · production · leonidasv · 2020-12-14 · source ↗ · wrong label?“the web-app (GCP) we use and still, this mess is the best they can give us.”
regret · production · Traubenfuchs · 2020-12-09 · source ↗ · wrong label?“it works and it's fast enough for the things I need to do”
endorse · production · markbnj · 2020-12-09 · source ↗ · wrong label?“simply not leaving the gcp login backdoor open”
regret · production · paulfurtado · 2020-08-20 · source ↗ · wrong label?“Then we moved to GCP... (AWS's offering was far better than GCP's) ... GCP makes this easier than AWS”
mixed · production · secondcoming · 2020-08-16 · source ↗ · wrong label?“They've been very helpful and if we have hard questions, we can ping them.”
endorse · production · lima · 2020-05-19 · source ↗ · wrong label?“we switched to Google Cloud, which has a better UI for telling you how much you're about to spend.”
endorse · production · mepiethree · 2020-04-01 · source ↗ · wrong label?“I wish all of GCP could be managed as Kubernetes objects.”
mixed · production · atombender · 2020-03-04 · source ↗ · wrong label?“until we went to AWS/GCP: Infra needs were highly manual”
endorse · production · blaird · 2020-01-09 · source ↗ · wrong label?“GCE even allows you to use the same boot disk, if mounted read-only, for multiple instances, perfect for these type of images.”
endorse · production · andoma · 2019-12-24 · source ↗ · wrong label?“GCP TPU options beat the pants off of everyone. I love bigquery.”
endorse · production · alexnewman · 2019-12-17 · source ↗ · wrong label?“I just happen to think GCP has the most cutting edge cloud native technologies and services”
endorse · production · 6 yr · devy · 2019-12-17 · source ↗ · wrong label?“At my company, we use all major 3 clouds. The GCP support is super fast. The GCP price is better than other two.”
endorse · production · tzury · 2019-12-17 · source ↗ · wrong label?“I actually played around with deploying it using GCP and had issues due to the logging”
regret · personal · photon_lines · 2019-12-06 · source ↗ · wrong label?“in AWS/GCP they were able to 10x that with similar server specs”
endorse · production · victor106 · 2019-05-03 · source ↗ · wrong label?“So, we use GCP Azure AWS exclusively because of their ability to defy network level ddos.”
endorse · production · InGodsName · 2018-12-26 · source ↗ · wrong label?“We chose Google Cloud Platform because we believe that they offer the most reliable cloud platform for our workload”
endorse · production · dsumenkovic · 2018-12-10 · source ↗ · wrong label?“I have been using Google Cloud for many years now. I used it because I thought it was technically superior than AWS and several others.”
endorse · personal · speedplane · 2018-11-30 · source ↗ · wrong label?“we've migrated ~50-100 VMs to GCP and I love the GCP products. ... So much cheaper (in our case we saved ~60%)”
endorse · production · luka-birsa · 2018-11-16 · source ↗ · wrong label?“Google has great primitives. But they are very slow in releasing new features”
mixed · production · manigandham · 2018-11-14 · source ↗ · wrong label?“All in all, our GCP spend is about 20% less than our AWS spend was. We're getting a lot more utility for a little less money.”
endorse · production · halbritt · 2018-10-02 · source ↗ · wrong label?“We chose Google Cloud Platform because we believe that they offer the most reliable cloud platform for our workload”
endorse · production · dsumenkovic · 2018-09-20 · source ↗ · wrong label?“I simply wish if Google Support was better or at least they had a more proactive status page update policy.”
regret · production · ksajadi · 2018-07-12 · source ↗ · wrong label?“We run on GCP/GKE and aren't moving... Azure comes close but GCP is very far behind. What's there is nice and well designed, but leaves a lot of gaps”
mixed · production · manigandham · 2017-11-30 · source ↗ · wrong label?“We moved to Google Cloud Platform. Snark aside, we're continuing to be pretty happy about that decision, in addition to paying a lot less.”
endorse · production · endymi0n · 2017-10-30 · source ↗ · wrong label?“I'm so glad we switched 90% of our stack to Google.”
endorse · production · endymi0n · 2017-09-27 · source ↗ · wrong label?“That's not only technically impressive, it's also really good customer service.”
endorse · personal · runeks · 2016-12-17 · source ↗ · wrong label?“Recently moved behind cloudflare because google cloud did not protect us from attacks like the UDP floods which didn't even reach our servers.”
regret · production · wesleytodd · 2016-08-28 · source ↗ · wrong label?“I was involved in recently migrating to GCP and it has worked wonderfully for us thus far.”
endorse · production · 76bd · 2016-08-23 · source ↗ · wrong label?“As someone who worked at a company that used almost all of the GCP products, I agree with just about everything in this article. GCP is pretty amazing”
mixed · production · brechin · 2016-08-05 · source ↗ · wrong label?“We run LAMP (Linux-Apache-MySQL-PHP) stacks on virtual machine instances on servers worldwide of our choosing.”
endorse · production · kaa2102 · 2015-10-04 · source ↗ · wrong label?“I have reached with the ssh door a Google Cloud Box where the 27B model ran with an L4 g2-standard-16.”
neutral · personal · guregodevo · 2026-11-01 · source ↗ · wrong label?“went down for 30 minutes due to a GCP migration to a new project and we screwed up a secret in prod.”
neutral · production · watty · 2026-08-19 · source ↗ · wrong label?“We build every component directly from source in a SLSA 3 environment we run (mostly in GCP).”
neutral · production · morellonet · 2026-06-24 · source ↗ · wrong label?“We migrated our whole stack to GCP in about a week.”
neutral · production · mfrye0 · 2026-02-18 · source ↗ · wrong label?“We use a mix of Google Cloud and Telekom Cloud for some of our more picky customers in Germany.”
neutral · production · jillesvangurp · 2025-12-20 · source ↗ · wrong label?“I bought GDP Premium and configured GCP, setup environment variables”
neutral · personal · jaigupta · 2025-12-18 · source ↗ · wrong label?“I used to work at GCP... I had to migrate our startup from GCP to Azure”
neutral · production · nosefrog · 2025-03-01 · source ↗ · wrong label?“We migrated from GCP to AWS when our free GCP credits from YC ran out”
neutral · production · rozap · 2024-11-27 · source ↗ · wrong label?“We run on Google Cloud, AWS, and our own hardware now since middle of this year”
neutral · production · justjake · 2024-11-26 · source ↗ · wrong label?“we setup a separate archive account on AWS for backups and also made an extra copy on GCP as our off prem equivalent”
neutral · production · adrianco · 2024-05-10 · source ↗ · wrong label?“we run a build machine for when developers push their code into a PR and we build a binary/container”
neutral · production · lawrjone · 2023-12-29 · source ↗ · wrong label?“My company has invested in moving to Azure except where we need to stay on Google.”
neutral · production · RoyTyrell · 2023-12-14 · source ↗ · wrong label?“We use Alibaba Cloud, GCP, and most of all AWS.”
neutral · production · renewiltord · 2023-12-13 · source ↗ · wrong label?“Our internal application logs were already being scooped up by GCP because we run our services in GKE”
neutral · production · bhyolken · 2023-11-17 · source ↗ · wrong label?“I have used GCP extensively since about 2009.”
neutral · production · 14 yr · latchkey · 2023-10-26 · source ↗ · wrong label?“switched to hosted solutions from AWS and Google cloud.”
neutral · production · jml78 · 2023-08-10 · source ↗ · wrong label?“the client's GCP project we were using along with the architects”
neutral · production · anshumankmr · 2022-12-17 · source ↗ · wrong label?“We run our Spring/Kotlin JVM servers on cheap vms in Google cloud and in another data center using openstack.”
neutral · production · jillesvangurp · 2022-07-22 · source ↗ · wrong label?“AWS's archaic account model is one reason we've switched to GCP.”
neutral · production · dhess · 2022-07-02 · source ↗ · wrong label?“we switched multiple times, from Azure to Google Cloud to AWS, chasing those startup credits.”
neutral · production · kevin_nisbet · 2022-04-07 · source ↗ · wrong label?“This scenario where we migrated clouds has been pretty similar between IBM, Oracle, Azure, GCP and also AWS.”
neutral · production · oneplane · 2022-02-11 · source ↗ · wrong label?“We run entirely on the Cloud (no physical offices or data centers) and honestly, some minimal GCP/AWS best practices”
neutral · production · thraxil · 2021-12-20 · source ↗ · wrong label?“There are at least 6 cloud providers I can name that I've used which run their own data centers”
neutral · production · george3d6 · 2021-12-07 · source ↗ · wrong label?“Now we spend 7 figures on GCP instead.”
neutral · production · jordanthoms · 2021-04-12 · source ↗ · wrong label?“We migrated from aws to google cloud.”
neutral · production · throw20210211 · 2021-02-11 · source ↗ · wrong label?“42 <-- different types of Google Cloud resources we use in our Terraform configs.”
neutral · production · yegle · 2020-12-25 · source ↗ · wrong label?“deploy it on yet another VM on GCP or something for their users.”
neutral · production · Jugurtha · 2020-12-22 · source ↗ · wrong label?“Our final, most costly, GCP spend, including support contract = about $2000/mo”
neutral · production · p_l · 2020-11-23 · source ↗ · wrong label?“the other services we run on GCP put us well past whatever it might include.”
neutral · production · thraxil · 2020-11-04 · source ↗ · wrong label?“I built it to deal with GCP infrastructure (private networking and Cloud Run).”
neutral · production · neomantra · 2020-11-03 · source ↗ · wrong label?“Geo has been used in the past when we migrated to Google Cloud if I remember correctly.”
neutral · production · YorickPeterse · 2020-06-23 · source ↗ · wrong label?“One of the reasons we moved to GCP from AWS”
neutral · production · MightySCollins · 2020-03-04 · source ↗ · wrong label?“We moved to GCP from AWS because we thought it'd be cheaper. Turns out it wasn't that much cheaper at all.”
neutral · production · dirtydroog · 2020-02-25 · source ↗ · wrong label?“We nuked our drives and sold the rest to a liquidation company when we moved to GCP.”
neutral · production · scarejunba · 2019-12-17 · source ↗ · wrong label?“Hosted on GCP kubernetes, using 0.25 cpu and 250 mem”
neutral · production · meztez · 2019-12-16 · source ↗ · wrong label?“I worked with them when we moved to GCP.”
neutral · production · macspoofing · 2019-11-21 · source ↗ · wrong label?“Models report a finished state over Kafka after getting persisted to buckets in Google cloud”
neutral · production · NegatioN · 2019-11-12 · source ↗ · wrong label?“we run several Kubernetes clusters via GKE on Google Cloud Platform”
neutral · production · atombender · 2019-08-23 · source ↗ · wrong label?“My company switched from VMs to a managed k8s cluster (gcloud).”
neutral · production · zsoltk · 2019-08-23 · source ↗ · wrong label?“Reliability is ensured with multiple points of presence using the Google Cloud infrastructure.”
neutral · production · lpellegr · 2019-08-12 · source ↗ · wrong label?“We run the infrastructure in the cloud (we run it on GCP using Postgres and k8s, but will likely go multicloud at some point).”
neutral · production · pbiggar · 2019-07-09 · source ↗ · wrong label?“I have been using AWS and GCP for a while now and was thinking about getting the certifications”
neutral · personal · chirau · 2018-12-23 · source ↗ · wrong label?“Tech Lead of Google Registry here. We run on GCP.”
neutral · production · CydeWeys · 2018-10-16 · source ↗ · wrong label?“having burnt through our GCP credits, we are again making a switch.”
neutral · production · rgun · 2018-09-16 · source ↗ · wrong label?“we switched from AWS to GCP for cost reasons, and I implemented an abstraction (similar to go-cloud's) between S3 and GCS”
neutral · production · fishywang · 2018-07-24 · source ↗ · wrong label?“We’re not a big Google customer, couple thousand a month, but when we migrated we instantly reached out to account reps”
neutral · production · johlindenbaum · 2018-06-30 · source ↗ · wrong label?“I've been using GCP for a few months for free (you get $300 credit when you first sign up)”
neutral · personal · fourmii · 2017-11-29 · source ↗ · wrong label?“We run on Google and it would be nice to have a separate project for managed databases while taking advantage of our existing billing arrangements”
neutral · production · manigandham · 2017-11-06 · source ↗ · wrong label?“we run a relatively small kafka cluster on GCP and it's pretty much hassle-free.”
neutral · production · jurre · 2017-11-01 · source ↗ · wrong label?“we run on GCP but use Azure event hubs”
neutral · production · manigandham · 2017-10-04 · source ↗ · wrong label?“NPTEL (the platform, like coursera...) then got GCP credits so we migrated it.”
neutral · production · tango12 · 2017-04-05 · source ↗ · wrong label?“we made this decision before we moved to GCP, but we are also not fans of using platform lock-in.”
neutral · production · Vishnevskiy · 2017-01-20 · source ↗ · wrong label?“It was ultimately faster than Route 53 and Google Cloud (the path we ended up going).”
neutral · personal · thefarseeker · 2017-01-10 · source ↗ · wrong label?“We set up StrongSwan recently to use as a VPN into Google Cloud”
neutral · production · lobster_johnson · 2016-12-25 · source ↗ · wrong label?“While I use some Google products (AppEngine, GCP, Play movies+music)”
neutral · personal · mark_l_watson · 2016-12-16 · source ↗ · wrong label?“We've switched over 20 nodes to Google Cloud for the time being”
neutral · production · houseofmore · 2016-01-02 · source ↗ · wrong label?“we run a huge Cassandra install in multi dacenters on GCP.”
neutral · production · samkone · 2015-06-05 · source ↗ · wrong label?