I like how Gravity Cloud helps reduce our monthly overhead by providing granular, real-time visibility into the cost of every active environment, which helps us cut out wasted resources. I appreciate that it completely removes the traditional 'DevOps bottleneck' by enabling developers to provision servers, databases, or testing environments without waiting on an operations engineer. I enjoy how it connects directly with AWS, including AWS Lambda and Amazon S3, as well as Google Cloud Platform (GCP) and Microsoft Azure. I find it valuable that Gravity Cloud abstracts away the complexity of managing Kubernetes manually, eliminating the need to write endless YAML files and manage Helm charts by hand. The platform allows our developers to self-serve infrastructure needs, which is perfect for our growing engineering team. Review collected by and hosted on G2.com.
While the platform helps reduce wasted cloud resources (like forgotten AWS instances), Gravity Cloud’s own pricing tiers can become quite expensive as a team grows, adds more seats, and scales up its operations. Highly valuable features, such as granular Cloud Cost Management and SOC2 compliance, are locked behind the more expensive tiers. Allowing teams on the lower tiers to purchase these specific features as individual add-ons would give startups much-needed flexibility without forcing a massive plan upgrade. Additionally, the initial wiring is generally considered the hardest part. Connecting Gravity Cloud to your existing AWS or GCP accounts, linking your Git repositories, configuring Kubernetes clusters, and setting up complex Role-Based Access Control (RBAC) takes dedicated time and effort. Review collected by and hosted on G2.com.
