Softwr

Cloud · head to head

Qovery vs Wiz

Qovery logo

Qovery

Cloud

Deployment platform that provisions and operates Kubernetes inside your own cloud account

From
On request
Rated
-
Wiz logo

Wiz

Cloud

Cloud and AI security platform unifying code, cloud, and runtime protection.

From
On request
Rated
-

The short version

  • Each has a real cost: Qovery no plan publishes a price, deployment minute overage rates are not disclosed, and there is a 14 day trial rather than a free tier, so you cannot budget or compare against alternatives without going through sales.; Wiz no public pricing; licensing requires a custom quote based on workloads and sensors.
  • They diverge on capability: Qovery covers Bring your own cloud, Wiz covers Cloud security posture management.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Qovery and Wiz actually diverge.

Attributes where Qovery and Wiz differ
AttributeQoveryWiz
PlatformsWeb, CLI, REST API, Kubernetesweb, api

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Cloud).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Qovery

  • Bring your own cloud
  • Preview environments
  • Cluster lifecycle
  • Terraform provider
  • MCP server
  • Policy as code

Only in Wiz

  • Cloud security posture management
  • Code security (Wiz Code)
  • Runtime threat detection (Wiz Defend)
  • AI security agents
  • AI workload protection
  • Attack path analysis

What people use each for

The jobs each tool is most often brought in to do.

Qovery

  • A regulated business that must keep application data inside its own AWS account but has nobody to build a deployment platformnot Wiz
  • Giving twenty engineers preview environments per pull request without writing and maintaining Terraform and Helm by handnot Wiz
  • Standardising deployment across AWS and GCP when acquisitions have left the organisation on two cloudsnot Wiz
  • Replacing a managed platform when data residency rules put every hosted option out of reachnot Wiz

Wiz

  • Identifying cloud misconfigurations across multi-cloud environmentsnot Qovery
  • Securing code from IDE through CI/CD deploymentnot Qovery
  • Detecting and responding to active threats at runtimenot Qovery
  • Governing AI workloads and models in the cloudnot Qovery
  • Prioritizing risk with cross-environment attack path analysisnot Qovery

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Qovery

  • No plan publishes a price, deployment minute overage rates are not disclosed, and there is a 14 day trial rather than a free tier, so you cannot budget or compare against alternatives without going through sales.
  • The GPL-3.0 engine and console do not constitute a self-hostable product, because the control plane and API are closed and the self-hosted option is gated behind Enterprise, so the open licence gives you no exit if the company changes direction.
  • Qovery provisions managed Kubernetes into your account, which means the cloud bill sits on top of the licence and Qovery initiates control plane and ingress controller upgrades on infrastructure your team is accountable for.
  • The company repositioned to agentic infrastructure in June 2026 and now ships a deployment platform, a browser development portal and autonomous coding agents concurrently, so a buyer of the deployment product is not at the centre of the roadmap.
  • Team and Business are capped at two and three connected clusters with fixed 4 vCPU CI runners and no single sign-on on Team, which pushes teams of moderate size onto quoted Enterprise pricing earlier than the plan names imply.

Wiz

  • No public pricing; licensing requires a custom quote based on workloads and sensors.
  • Modular licensing across Cloud, Code, Defend, and Sensor products can complicate cost planning.
  • Full runtime protection value depends on deploying Wiz Sensor agents, adding operational overhead.
  • Primarily aimed at mid-to-large enterprises despite the smaller Wiz Go bundle.

Pricing, plan by plan

Qovery

On request
  • Team$undefined/year
    • Billed on usage with no published rate card
    • 10 users, up to 100 environments, 2 connected clusters
    • 5,000 deployment minutes and 7 day audit logs
  • Business$undefined/year
    • Billed on usage with no published rate card
    • 20 users, up to 250 environments, 3 connected clusters
    • 10,000 deployment minutes and 30 day audit logs
  • Enterprise$undefined/year
    • Custom users, environments and clusters
    • Self-hosted or air-gapped control plane
    • On-premises and bring-your-own-Kubernetes

Wiz

On request

No published plan breakdown. See the Wiz review.

Which should you pick?

Choose Qovery if

  • You need bring your own cloud.
  • You work on Web, CLI, REST API, Kubernetes.
  • You also want preview environments.

Choose Wiz if

  • You need cloud security posture management.
  • You work on web, api.
  • You also want code security (wiz code).

Questions people ask

Is Qovery or Wiz better?
Neither clearly leads. Qovery starts at On request and Wiz at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Qovery or Wiz?
Qovery starts at On request and Wiz at On request.
Does Qovery or Wiz run on more platforms?
Qovery runs on Web, CLI, REST API, Kubernetes. Wiz runs on web, api.
What is Qovery best used for?
Qovery is most often used for a regulated business that must keep application data inside its own aws account but has nobody to build a deployment platform, giving twenty engineers preview environments per pull request without writing and maintaining terraform and helm by hand, standardising deployment across aws and gcp when acquisitions have left the organisation on two clouds, replacing a managed platform when data residency rules put every hosted option out of reach. Of those, a regulated business that must keep application data inside its own aws account but has nobody to build a deployment platform and giving twenty engineers preview environments per pull request without writing and maintaining terraform and helm by hand are not what Wiz is typically brought in for.
What can Qovery do that Wiz cannot?
Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider. Wiz covers Cloud security posture management, Code security (Wiz Code), Runtime threat detection (Wiz Defend), AI security agents.

Answered from the vendors’ own pages

Qovery: Does Qovery run my applications on its own servers?

No. It provisions and operates Kubernetes inside your AWS, GCP, Azure or Scaleway account, so compute and data stay with your cloud provider and that bill is entirely separate from the Qovery licence.

Wiz: How much does Wiz cost?

Wiz does not publish standard pricing. The platform uses modular licensing based on workloads, active developers, log ingestion, or sensors. All pricing requires requesting a custom quote directly from the company.

Source
Qovery: Can I self-host Qovery?

Only on Enterprise. The deployment engine and console are GPL-3.0, but the control plane is closed source and the self-hosted and air-gapped deployments are commercial Enterprise features.

Wiz: Does Wiz offer a free trial?

No free trial information is mentioned on Wiz's pricing page. Pricing is determined by custom quote based on organizational needs.

Source
Qovery: What does it cost?

Qovery does not publish a rate card. Team and Business are billed on usage and quoted through sales, and Enterprise is fully custom. There is a 14 day trial with no card required.

Wiz: What products does Wiz offer?

Wiz provides five modular licensing options: Wiz Cloud, Wiz Code, Wiz Defend, Wiz Sensor, and Wiz Go Bundle for SMBs, allowing organizations to scale based on specific security requirements.

Source
Qovery: What survives if I stop paying?

The Kubernetes cluster and the workloads keep running in your cloud account, but you lose the console, the deployment pipeline, preview environments and every process built on top of them.

Share

Related pages

Other head to heads