Developer Tools · head to head
Fig vs Qovery
Fig
Developer Tools
IDE-style autocomplete for your existing terminal
- From
- Free
- Free plan
- Yes
Qovery
Cloud
Deployment platform that provisions and operates Kubernetes inside your own cloud account
- From
- On request
- Free plan
- No
The short version
- Only Fig has a free tier, so it costs nothing to try first.
- Each has a real cost: Fig shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete; 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.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Fig and Qovery actually diverge.
Identical on both: user rating (Not yet rated).
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 Fig
Nothing recorded that Qovery does not also cover.
Only in Qovery
- Bring your own cloud
- Preview environments
- Cluster lifecycle
- Terraform provider
- MCP server
- Policy as code
What people use each for
The jobs each tool is most often brought in to do.
Fig
No use cases recorded yet. See the Fig review.
Qovery
- A regulated business that must keep application data inside its own AWS account but has nobody to build a deployment platformnot Fig
- Giving twenty engineers preview environments per pull request without writing and maintaining Terraform and Helm by handnot Fig
- Standardising deployment across AWS and GCP when acquisitions have left the organisation on two cloudsnot Fig
- Replacing a managed platform when data residency rules put every hosted option out of reachnot Fig
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Fig
- Shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete
- The standalone desktop app is no longer available or supported
- The completion specs remain open source on GitHub, but the product that consumed them is gone
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.
Pricing, plan by plan
Fig
FreeNo published plan breakdown. See the Fig review.
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
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.
Questions people ask
- Is Fig or Qovery better?
- Neither clearly leads. Fig starts at Free and Qovery at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Fig or Qovery?
- Fig has a free tier; the other does not. Paid plans start at Free for Fig and On request for Qovery.
- Does Fig or Qovery run on more platforms?
- Fig runs on Web. Qovery runs on Web, CLI, REST API, Kubernetes.
- Can I use Fig for free?
- Yes. Fig has a free tier, so you can try it without paying. Qovery starts at On request.
- What can Fig do that Qovery cannot?
- Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider.
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.
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.
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.
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.
Related pages
Other head to heads
- Fig vs Visual Studio Code
- Fig vs ESLint
- Fig vs Turborepo
- Fig vs pnpm
- Fig vs Sweep
- Fig vs Cody
- Fig vs Warp
- Fig vs Keycloak
- Fig vs Rust
- Fig vs CodeSandbox
- Fig vs Vite
- Fig vs Daytona
- Fig vs Visual Studio
- Fig vs Xlinesoft
- Fig vs Ona (formerly Gitpod)
- Fig vs Sourcegraph
- Fig vs Render
- Fig vs Porter
- Fig vs Northflank
- Fig vs CapRover
- Fig vs Coolify
- Fig vs Railway
- Fig vs Dokku
- Fig vs Scaleway
- Fig vs Portworx
- Fig vs Podman
- Fig vs containerd
- Fig vs Encore
- Fig vs Oracle Cloud
- Fig vs Orca Security
- Fig vs Packer
- Fig vs OpenTelemetry
- Fig vs Rook
- Qovery vs Visual Studio Code
- Qovery vs ESLint
- Qovery vs Turborepo
- Qovery vs pnpm
- Qovery vs Sweep
- Qovery vs Cody
- Qovery vs Warp
- Qovery vs Keycloak
- Qovery vs Rust
- Qovery vs CodeSandbox
- Qovery vs Vite
- Qovery vs Daytona
- Qovery vs Visual Studio
- Qovery vs Xlinesoft
- Qovery vs Ona (formerly Gitpod)
- Qovery vs Sourcegraph
- Qovery vs Render
- Qovery vs Porter
- Qovery vs Northflank
- Qovery vs CapRover
- Qovery vs Coolify
- Qovery vs Railway
- Qovery vs Dokku
- Qovery vs Scaleway
- Qovery vs Portworx
- Qovery vs Podman
- Qovery vs containerd
- Qovery vs Encore
- Qovery vs Oracle Cloud
- Qovery vs Orca Security
- Qovery vs Packer
- Qovery vs OpenTelemetry
- Qovery vs Rook