Commercial Kubernetes platforms
Anyport vs Qovery
Qovery's centre of gravity is a cloud account. Give it credentials for AWS, GCP, Azure or Scaleway and it provisions and operates a Kubernetes cluster for you, which is a genuinely different offer from ours: we never create infrastructure.
They also have a bring-your-own-Kubernetes path for clusters you manage yourself, so if you have a cloud account the two products overlap more than the rest of this page suggests, and you should compare them on features rather than on reachability.
What both of them do
This much is common ground, so the table below is only about where they differ.
- A hosted control plane in front of Kubernetes you own.
- Your workloads and data stay in your own infrastructure.
- Builds from Git, environments and preview deployments.
- Roles, an audit log and one console over several clusters.
Where they differ
The short answer first, and the detail underneath it where the short answer would otherwise mislead.
| Qovery | Anyport | |
|---|---|---|
| What it is | Qovery It provisions and operates the cluster In your cloud account, with a BYOK path alongside. | Anyport It connects to a cluster you run Wherever that cluster happens to be. |
| Runtime | Qovery Kubernetes, managed by Qovery On AWS, GCP, Azure or Scaleway. | Anyport Kubernetes, managed by you Anyport can install k3s on a bare machine if you do not have a cluster. |
| Where the control plane runs | Qovery Hosted by Qovery | Anyport Hosted by us There is nothing for you to install, upgrade or back up. |
| How it reaches your infrastructure | Qovery Cloud credentials you supply Or the documented BYOK path. | Anyport Your cluster connects out The agent dials us. No credentials of yours are held. |
| What your infrastructure must expose | Qovery A cloud account it can provision in We have not verified what the BYOK path requires. | Anyport Nothing No inbound port, no public IP, no reachable API server. |
| Who provisions the cluster | Qovery Qovery does In your account, and then it operates it. | Anyport You do We never create infrastructure or take cloud credentials. |
| Price | Qovery Published, plus your cloud bill You pay for what it provisions on your behalf. | Anyport Free today Up to 10 private and 20 public clusters. Compute is never metered. |
| Compliance | Qovery See their trust page | Anyport Not certified yet Controls are published in full on the security page instead. |
What Qovery is
Taken from their own documentation, read on 4 September 2026.
Qovery's documented starting point is a cloud provider account with credentials. It supports AWS, GCP, Azure and Scaleway, and provisions a managed Kubernetes cluster in roughly thirty minutes.
It also documents a bring-your-own-Kubernetes option for connecting a cluster you manage yourself, including on-premises. We have not verified what that path requires of the cluster's network, so this page does not claim anything about it.
The product is aimed at teams who want an internal developer platform without building one, with environments, preview environments and a service catalogue on top of Kubernetes.
Choose Qovery if
- You want somebody else to create and operate the Kubernetes cluster, not just what runs on it.
- Your infrastructure is in AWS, GCP, Azure or Scaleway and you are content to hand over credentials to it.
- You want a longer-established vendor with a larger team behind the product.
Choose Anyport if
- There is no cloud account. The cluster is on hardware you own, and nothing is going to provision it for you.
- You do not want to hand a platform credentials that can create infrastructure and bill you for it.
- The clusters are unreachable from outside, or belong to customers whose networks you do not control.
- You want the control plane to hold no standing access into the cluster.
Questions
- Does Qovery need cloud credentials?
- For its main path, yes. Qovery's documented starting point is a cloud provider account it provisions a managed Kubernetes cluster in. It also documents a bring-your-own-Kubernetes option for clusters you manage yourself.
- Does Anyport ever create infrastructure?
- No. Anyport never provisions servers, clusters or load balancers, and holds no cloud credentials. The one exception is installing k3s on a machine you point it at, which happens on that machine and creates nothing.
- What does Anyport require of a cluster?
- A Kubernetes cluster you can run one command against, or a bare Linux machine where Anyport installs k3s first. No inbound port, no public IP, no load balancer that can obtain one, and no kubeconfig handed to us. The agent opens a connection outward and holds it open.
- What does Anyport cost?
- Every feature is free today, for everyone on your team, on up to 10 private clusters and 20 public ones. Compute is never metered because it is not ours. The one counted resource is traffic our gateway carries for clusters with no public address of their own, with an allowance of 10 GiB a month.
- Is Anyport audited or certified?
- Not yet. In place of a report, the security page documents what the agent runs with inside your cluster, what crosses the boundary and how secrets are stored, so a reviewer can evaluate the controls directly. Two of them hold regardless of certification: we never receive credentials for your Kubernetes API, and your workloads keep serving whether or not our control plane is reachable.
Sources
Read on 4 September 2026. If one of these pages now says something different, the source is right and this page is stale.
If Anyport is the one you want
Connecting a cluster is one command and takes a few minutes. Everything is free today, and the pricing page lists the limits that are actually enforced rather than the ones a plan would imply.