Skip to content
← All comparisons

Commercial

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 in your account.

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.

01Common ground

What both of them do

This much both products do, 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.

02The differences

Where they differ

Each row asks one question and sets the two answers across a seam. The highlighted row is the one this comparison turns on.

Qovery

It provisions and operates the cluster

In your cloud account, with a BYOK path alongside.

What it is

Anyport

It connects to a cluster you run

Wherever that cluster happens to be.

Qovery

Kubernetes, managed by Qovery

On AWS, GCP, Azure or Scaleway.

Runtime

Anyport

Kubernetes, managed by you

Anyport can install k3s on a bare machine if you do not have a cluster.

Qovery

Hosted by Qovery

Where the control plane runs

Anyport

Hosted by us

There is nothing for you to install, upgrade or back up.

Qovery

Cloud credentials you supply

Or the documented BYOK path.

How it reaches your infrastructure

Anyport

Your cluster connects out

The agent dials us. No credentials of yours are held.

Qovery

A cloud account it can provision in

We have not verified what the BYOK path requires.

What your infrastructure must expose

Anyport

Nothing

No inbound port, no public IP, no reachable API server.

Qovery

Qovery does

In your account, and then it operates it.

Who provisions the cluster

Anyport

You do, or Anyport Cloud does

Never in your account: we take no cloud credentials. Anyport Cloud runs clusters on Anyport's own hardware.

Qovery

$2,999 a month on Business

Billed yearly, 20 users, up to 3 clusters, then $399 a month per additional cluster. Compute is not metered, but deployment minutes are: 10,000 included, then $0.16 a minute. Checked 2 October 2026.

Price

Anyport

$5/mo or $50/yr

3 clusters free, then $2 a month each, billed by the hour. Compute on your own clusters is never metered.

Qovery

SOC 2, GDPR

The compliance scope listed on their pricing page.

Compliance

Anyport

Not certified yet

Controls are published in full on the security page instead.

03The decision

Which one to choose

Each list is written to be true. If the first one describes you, the better product is theirs.

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.

04In their words

What Qovery is

Taken from their own documentation and pricing.

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.

05Questions

Questions people ask

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?

Not in your account. Anyport never provisions servers, clusters or load balancers there, and holds no cloud credentials. Installing k3s on a machine you point it at happens on that machine and creates nothing. The separate case is Anyport Cloud, where Anyport runs a cluster for you on its own hardware and bills what it uses.

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. With no cluster at all, Anyport Cloud runs one for you on Pro, billed for what your apps use.

What does Anyport cost?

Three clusters are free with every feature and unlimited members, apps and projects. Pro is $5 a month with $5 of credit back each month; clusters past the free three are $2 a month each, and clusters on Anyport Cloud $5, billed by the hour. Compute on your own clusters is never metered because it is not ours, and the one counted resource there is traffic our gateway carries for clusters with no public address of their own: 10 GB a month free, 100 GB on Pro, then $0.02 per GB. A cluster on Anyport Cloud runs on our hardware instead and is billed for what your apps use, at $12 per vCPU and $6 per GiB of memory a month, from credit.

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.