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
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
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 focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)