Early Access For Google Cloud Platform
What is Qovery?
For the uninitiated, Qovery is a platform that serves over 50,000 developers and numerous companies by simplifying application deployment across various clouds. With existing support for Amazon Web Services (AWS) and Scaleway, we're adding GCP as our third supported cloud platform.
Our Core Offerings
Production Deployments: Make deployments for engineering teams in production hassle-free.
Preview Environments: Our preview environments product helps engineering teams test code changes in a sandboxed environment, making it easier to ensure quality before going live.
Internal Developer Platform: Empower your development teams with self-service infrastructure, making them more productive and efficient.
All those happy customers are using Qovery on AWS and Scaleway - now it's also possible on Google Cloud Platform (GCP).
Why Google Cloud Platform?
The addition of GCP support isn't just a new feature; it's a response to a growing demand from our community. It is, in fact, the most requested feature on our public roadmap, even from customers who are currently using AWS. What we hear most is the need to streamline infrastructure, enabling everything to be managed in one place.
One of the key advantages of our GCP support is that Qovery runs on top of Google Kubernetes Engine (GKE), leveraging its powerful orchestration and scaling capabilities. GKE's robust feature set aligns perfectly with Qovery’s goals to provide a seamless and efficient deployment experience.
GCP is renowned for its strengths in areas such as data analytics, machine learning, and open-source technologies, making it a natural fit for Qovery's offerings. With its global reach, innovative services, and reliable, scalable infrastructure, GCP perfectly complements our existing support for AWS and Scaleway.
Early Access and Roadmap
We're thrilled to offer companies an exclusive opportunity to join our Early Access program for GCP support.
Timeline
- 1️⃣ Early Access is Available Now: Companies can apply for early access starting today.
- 2️⃣ Public Beta Release in early December: We're targeting a public beta release in early December 2023.
- 3️⃣ Stable Release in Mid-January 2024: A stable version is expected to be available by mid-January 2024.
How to Apply for Early Access?
- Visit our Early Access Page.
- Complete the application form to register your interest.
- Our team will contact you for the next steps.
We're waiting for you ✨
As we expand Qovery's reach to include GCP, we remain steadfast in our commitment to make cloud deployment as easy as possible. We're excited about the new opportunities that GCP support will bring to our community, and we invite you to be part of this exciting journey!
.svg)
.svg)
.svg)
Suggested articles
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes is an open-source container orchestration engine. At enterprise scale, it abstracts infrastructure to automate deployment, scaling, and networking. However, managing hundreds of clusters introduces severe Day-2 operational toil, requiring agentic control planes to enforce global governance, security policies, and cost optimizations across multi-cloud fleets.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
.webp)