Softwr

Databases · head to head

Convex vs Qovery

Convex logo

Convex

Databases

Reactive backend combining a document database, TypeScript server functions and live queries, source-available under the Functional Source Licence.

From
Free
Free plan
Yes
Qovery logo

Qovery

Cloud

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

From
On request
Free plan
No

The short version

  • Convex starts at $25/mo; Qovery prices on request.
  • Only Convex lists reactive queries; only Qovery lists bring your own cloud.
  • Prices and features on this page were last checked on 13 November 2026.

How do Convex and Qovery differ?

Convex and Qovery differ on starting price (Free against On request), pricing model (Subscription against Quote) and free tier (Yes against No). Only the attributes on which Convex and Qovery actually diverge.

Attributes where Convex and Qovery differ
AttributeConvexQovery
Starting priceFreeOn request
Pricing modelSubscriptionQuote
Free tierYesNo
PlatformsWebWeb, API, Self-hosted
CategoryDatabasesCloud

Which features does each one have?

They share no listed features; 10 appear only for Convex and 6 only for Qovery. 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 Convex

  • Reactive queries
  • TypeScript server functions
  • ACID transactions
  • Document database
  • Scheduling and workflows
  • File storage
  • Text and vector search
  • End-to-end types

Only in Qovery

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

What is each one used for?

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

Convex

  • Collaborative applications where several users see the same data and every client must reflect a change immediatelynot Qovery
  • Agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cachenot Qovery
  • Small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineersnot Qovery
  • Prototypes that must become production without a rewrite of the data layer, where end-to-end TypeScript types remove a class of integration bugsnot Qovery

Qovery

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

Where do Convex and Qovery fall short?

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

Convex

  • The Functional Source Licence is not an OSI open source licence: competing use is prohibited until each release reaches its second anniversary and converts to Apache 2.0, so you may self-host but you may not build a service on it
  • Transactions are bounded at one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written, so every backfill, migration or bulk import has to be chunked into scheduled batches rather than written as a single operation
  • There is no SQL and no query planner; you declare up to 32 indexes per table and traverse them, and joins are loops in TypeScript, so an unanticipated access pattern requires a schema and index change rather than a new query
  • It is not an analytical database, so reporting means streaming data out to a warehouse and BI tools cannot be pointed at Convex directly, which adds a pipeline the architecture diagram did not originally include
  • The application is written against Convex's function and client APIs rather than a standard protocol, so leaving means rewriting the data access layer and replacing the reactivity model, not repointing a connection string

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

How much do Convex and Qovery cost?

Convex has a free plan, with paid plans from $25/mo; Qovery is priced on request. Plan by plan below, from each vendor's own pricing page.

Convex

Free
  • Free & StarterFree
    • Supports 1-6 developers
    • Reactive database
    • File storage
  • Professional$25
    • Supports up to 20 developers
    • All Starter features
    • Log streaming
  • Business & Enterprise$2,500/month minimum
    • Supports 50+ developers
    • SAML/SSO
    • Service SLAs

Qovery

On request
  • TeamOn request
    • 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
  • BusinessOn request
    • 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
  • EnterpriseOn request
    • Custom users, environments and clusters
    • Self-hosted or air-gapped control plane
    • On-premises and bring-your-own-Kubernetes

Which should you pick?

Choose Convex if

  • You need reactive queries.
  • You want to start without paying.
  • You also want typescript server functions.

Choose Qovery if

  • You need bring your own cloud.
  • You work on Web, API, Self-hosted.
  • You also want preview environments.

Questions people ask

Is Convex or Qovery better?
Neither clearly leads. Convex 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, Convex or Qovery?
Convex has a free tier; the other does not. Paid plans start at Free for Convex and On request for Qovery.
Does Convex or Qovery run on more platforms?
Convex runs on Web. Qovery runs on Web, API, Self-hosted.
Can I use Convex for free?
Yes. Convex has a free tier, so you can try it without paying. Qovery starts at On request.
What is Convex best used for?
Convex is most often used for collaborative applications where several users see the same data and every client must reflect a change immediately, agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cache, small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineers, prototypes that must become production without a rewrite of the data layer, where end-to-end typescript types remove a class of integration bugs. Of those, collaborative applications where several users see the same data and every client must reflect a change immediately and agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cache are not what Qovery is typically brought in for.
What can Convex do that Qovery cannot?
Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database. Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider.

Answered from the vendors’ own pages

Convex: Is Convex open source?

It is source-available under FSL-1.1-Apache-2.0. You may read, modify and self-host it, but competing use is prohibited until each release converts to Apache 2.0 on its second anniversary.

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.

Convex: Can I self-host it?

Yes. The backend, dashboard and CLI can run on your own infrastructure, with most of the features of the cloud product. Self-hosted instances include a telemetry beacon that can be disabled.

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.

Convex: Does it support SQL?

No. Data is accessed through a TypeScript query builder over declared indexes. Relationships are traversed in code, which is explicit and type-safe but means no ad hoc querying.

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.

Convex: What happens if a mutation exceeds the limits?

It fails rather than running longer, so bulk work must be split into batches and scheduled. The limits are per transaction: one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written.

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.

Convex: How does reactivity actually work?

Queries are deterministic functions and Convex records the data each one read. When a mutation changes that data, affected queries are re-run and subscribed clients receive the new result, so cache invalidation is handled by the platform.

Share

Related pages

Other head to heads