Google Compute Engine Reviews & Product Details

One of the things I like most i like about Google Engine is that I can create highly customized machine types with exact CPU and memory specs based on the specific workloads. The live migration is also a massive advantage, as it keeps my instances running smoothly even during backend maintenance. Review collected by and hosted on G2.com.

While the core features are robust, I find that some of the documentation are outdated or lacks in-depth troubleshooting steps. I also find that the premium tech support cost can be quite high for smaller organizations that aren't on an enterprise level. Review collected by and hosted on G2.com.

What I like best about Google Compute Engine (GCE) is how cleanly it balances power, flexibility, and performance without getting in your way.

A few standout things for me:

• Custom machine types – you’re not forced into rigid instance sizes. Need more CPU but less RAM? Easy. That level of control saves money and fits real workloads better.

• Strong performance & networking – Google’s global network is genuinely fast and reliable. Low latency, solid bandwidth, and great for distributed systems.

• Live migration – VMs can be moved during host maintenance with little to no downtime. That’s huge for production stability.

• Deep integration with the Google ecosystem – works seamlessly with GKE, Cloud Storage, BigQuery, IAM, and monitoring. Everything feels designed to work together.

• Pricing transparency – per-second billing and sustained-use discounts kick in automatically, which is refreshing.

Overall, GCE feels very engineer-friendly: fewer arbitrary limits, more control, and infrastructure that just quietly does its job. Review collected by and hosted on G2.com.

What I dislike about Google Compute Engine (being honest, not dramatic 😅):

• Steep learning curve – GCE assumes you’re already comfortable with cloud concepts. IAM, networking, projects, VPCs… powerful, but not very beginner-friendly.

• IAM can feel overcomplicated – super granular (which is good), but figuring out the right role vs too much access can be frustrating.

• Console UX is cluttered – the web console tries to do everything at once. Simple tasks sometimes take more clicks than they should.

• Support isn’t great unless you pay – community docs are solid, but real-time help or faster resolution usually means a paid support plan.

• Unexpected costs if you’re not careful – things like egress traffic, static IPs, and idle resources can quietly add up.

• Smaller ecosystem compared to AWS – fewer third-party tools, tutorials, and “copy-paste” solutions in some niches.

In short: GCE is excellent for engineers who know what they’re doing, but it can feel intimidating and a bit unforgiving if you’re new or moving fast without guardrails. Review collected by and hosted on G2.com.

I like that GCP feels like a modern solution where everything is fairly simple and clear. Unlike some other providers with a lot of legacy stuff, where you can spend hours trying to find what you need, GCP feels intuitive. Most of the time, I can figure out what I need and get it done within a few minutes without having to dig through a lot of documentation. Review collected by and hosted on G2.com.

I can’t really think of anything I genuinely dislike. Maybe the documentation could be better in some cases Review collected by and hosted on G2.com.

I really like the compatibility of Google Compute Engine with CI/CD pipelines and the capability of creating custom machines. It's great that I can choose my monitoring tools. It's very easy to create scalable and maintainable virtual machine clusters. The solution is also easy to use, which is why we chose it. Google Compute Engine has made efforts in security, making it easier to detect bot attacks and provide monitoring tools for GCP users. Review collected by and hosted on G2.com.

I think the protection against bots, especially cryptobots, could be improved. It has been an issue over the last year. I feel like GCP could do a better job with tools to protect against these threats. Review collected by and hosted on G2.com.

What I appreciate most about GCE is its emphasis on performance and the flexibility of its customizable VM architecture. One standout feature is live migration, which allows virtual machines to remain operational during maintenance, minimizing downtime—a capability that's uncommon among major providers. The per-second billing model ensures you only pay for the resources you actually use, adding to its cost-effectiveness. With custom machine types, you can precisely adjust CPU and RAM allocations rather than being limited to preset VM sizes. Networking performance is robust, which is particularly beneficial for distributed workloads and global deployments. Additionally, GCE offers deep integration with Google services, making it especially advantageous for AI/ML workloads, Kubernetes, and BigQuery. Altogether, these features make GCE a highly cost-efficient and reliable choice for production workloads, particularly for organizations that require flexibility and high uptime. Review collected by and hosted on G2.com.

One aspect I find frustrating about Google Compute Engine is the complexity of its pricing structure. The costs for custom machine types and network egress can accumulate quickly, and if you’re not keeping a close eye on your usage, it’s easy to end up spending more than intended. Review collected by and hosted on G2.com.

Google Compute Engine is reliable, secure and scalable platform to get direct access to Goggle finest compute. It has a lot of pricing tiers to match my requirement with a variety of RAM, storage and processing. Review collected by and hosted on G2.com.

The compute power of always free tier of compute engine is very low. It is unable to sustain a lot of traffic and might get down. Review collected by and hosted on G2.com.

What I like best about Google Compute Engine is the level of control it gives me without feeling overly complicated. I can choose exactly the machine type I need, including custom CPU and memory configurations, so I am not stuck paying for resources I will not use. The performance has been consistently solid, especially for compute heavy workloads, and the ability to scale up or down quickly makes it practical for both steady production systems and short term projects.

I also appreciate how well it integrates with the rest of the Google Cloud ecosystem. Networking, IAM, load balancing, and monitoring all work together in a way that feels cohesive rather than bolted on. Once everything is set up properly, it is reliable and predictable, which is exactly what I want from infrastructure. Review collected by and hosted on G2.com.

What I dislike about Google Compute Engine is that pricing can become confusing pretty quickly. Between sustained use discounts, committed use contracts, different machine families, and additional costs for storage, networking, and external IPs, it takes real effort to accurately predict monthly spend. If you are not actively monitoring usage, costs can creep up without much warning.

I also think the interface and overall experience can feel overwhelming, especially for newer users. There are a lot of configuration options, which is great for flexibility, but it also increases the learning curve. Troubleshooting can sometimes require digging through multiple services like VPC settings, firewall rules, and IAM policies, which adds complexity when something simple is not working as expected. Review collected by and hosted on G2.com.

Easy to spin up virtual machines quickly with custom configurations. Wide choice of machine types (general-purpose, compute-optimized, memory-optimized).Automatic sustained-use discounts reduce costs without manual effort.

Strong network performance with global infrastructure. Seamless integration with other Google Cloud services (BigQuery, Cloud Storage, Kubernetes).Good customer support

Ease of Implementation : Setting up virtual machines is simple and straightforward, whether you choose a predefined machine type or customize your own.

Frequency of Use: It works well for both occasional testing and frequent production workloads, making it highly versatile. Review collected by and hosted on G2.com.

The pricing structure can be confusing for beginners. Fewer predefined instance types compared to AWS EC2. Support costs extra unless you’re on an enterprise plan. Some features (like preemptible VMs) have limitations that make them tricky for long-term workloads. Learning curve if you’re new to Google Cloud. Review collected by and hosted on G2.com.

As a full-stack developer, I use Google Compute Engine a lot for application deployment and scaling. One of the best parts about GCE is the easy implementation; it's simple to set up VMs, and easy to integrate with Docker and Kubernetes, once you figure out the IAM stuff. I usually have a reliable experience with the platform over a lot of regular usage, especially taking advantage of the live migration and load balancing features. Customer service and documentation are usually pretty useful and consistently updated (though having some more in-depth troubleshooting would really help sometimes). Review collected by and hosted on G2.com.

The one issue I’ve faced with GCE is the complexity of IAM roles and permissions. While powerful, managing access control can feel overwhelming at first, especially when collaborating on multi-user projects. Review collected by and hosted on G2.com.

What I like best about Google Compute Engine (GCE) is its scalability, flexibility, and performance. Because I can quickly provision virtual machines with customized CPU, memory, and storage configurations to fit any workload, and GCE integrates seamlessly with other GCP services.

The infrastructure worldwide ensures high availability, and features such as live migration, automatic load balancing, and robust security make it reliable for both development and production environments.

This is something an upside I have felt as an upside while using the GCE in my projects. Review collected by and hosted on G2.com.

The one thing I hate most about the GCE is its "pricing structure," specifically when scaling multiple instances, because if you're doing the same thing on the AWS platform, it offers features like savings plans and reserved instances, which let you commit to usage over a period of time in exchange for lower prices. Review collected by and hosted on G2.com.