Convex Review 2026: Reactive Backend Pricing, Pros and Cons

Convex replaces the usual stack of database, API layer, websocket server and cron runner with one TypeScript backend. You write queries and mutations as functions, the client subscribes to them, and Convex pushes new results whenever the underlying data changes. That reactivity is the product, and it is also what you pay for.

This review is for developers and engineering leads choosing between Convex, Supabase, Firebase and Postgres-first options such as Neon. It covers how the platform works, what each plan costs per unit of usage, where the per-developer fee changes the comparison, and who should pick something else. Devshot runs no test lab, so every figure here comes from Convex's own pricing page and documentation, not from a trial deployment.

Convex is a hosted backend platform built around a reactive document database. Its pricing page lists file storage, text search, vector search, crons, webhooks, auth with more than 80 OAuth integrations and Node.js actions on every plan, including the free one, plus preview deployments and a selectable data region. The pitch is that a TypeScript developer never writes a REST layer or a cache-invalidation rule: the database knows which queries depend on which documents and re-runs them for subscribed clients.

Convex also lists an open-source edition you can self-host and develop against locally, plus an AI Gateway that calls major models through one API. The hosted service is the default path, and that is what this review prices.

Your backend lives in a convex folder as TypeScript functions. Queries read data and are cached and reactive, mutations write data inside a transaction, and actions call third-party APIs and can run on the Node.js runtime. A React, Next.js, React Native, Vue, Svelte, Python, Swift, Kotlin or Rust client calls those functions and, for queries, stays subscribed to them.

The limits shape the architecture. Per Convex's limits documentation, a query or mutation may run for 1 second of user code and read up to 16 MiB or 32,000 scanned documents, while Convex-runtime actions run for up to 30 minutes and Node actions up to 10. Heavy reporting queries therefore belong in actions or a separate analytics store, not in a live subscription.

Billing follows the same model. Every explicit client call, scheduled execution, subscription update and file access counts as a function call, and query and mutation compute is free on serverless deployments, so function calls, database storage, database I/O and egress are the lines that move the invoice.

Convex bills a per-developer fee plus metered resources, and the free plan is the only one with hard caps. Free and Starter share the same allowance: 1M function calls, 20 GB-hours of action compute, 0.5 GB of database storage, and 1 GB each of database I/O, file storage and egress a month. On Free, mutations that would write past the caps may fail; Starter keeps running and bills overage at $2.20 per extra million calls, $0.22 per extra GB of database storage or I/O and $0.132 per extra GB of egress. Professional raises the allowance to 25 times as many calls, 250 GB-hours of action compute, 50 GB each of database storage, I/O and egress, and 100 GB of file storage, at slightly lower overage rates.

Our arithmetic gives a clear upgrade point for a solo developer. At 12M function calls a month, Starter's call overage is $24.20, about the price of one Professional seat, and that seat includes more than twice that volume. Below that volume Starter is cheaper on calls alone; above it, Professional is cheaper and adds backups, log streaming and email support. Storage and egress overage shift the line, so price your own usage against both columns.

The per-developer fee is the line that grows with the team, not with the app. Four developers on Professional pay $100 a month before any overage, while Supabase's pricing page lists Pro with the first project included, further projects from $10 a month and no per-developer fee. Convex's limits apply per team, so adding a developer adds cost but not allowance. Deployments outside US regions are priced at 1.3x, per the limits documentation.

Business is a commitment, not a plan you drift into. Its monthly minimum works out to $30,000 a year and buys SAML SSO, service SLAs, custom roles, dedicated deployment classes and annual commit discounts. Pricing on this page is monthly: Convex shows no annual price for Free, Starter or Professional.

Methodology: we read Convex's pricing page and its limits documentation on October 19, 2026, with competitor prices from Supabase pricing, Firebase pricing, Neon pricing and Nhost pricing the same day. Scenario totals and break-even points are our arithmetic on those list prices, not quotes or benchmarks.

Convex fits a TypeScript team building a collaborative or live-updating product: dashboards, chat, multiplayer editors, AI agents that stream state to a UI. The reactive model removes the cache and websocket work that a Postgres stack needs, and the free plan's caps are high enough to launch a side project without a card.

A solo developer should start on Starter rather than Free once real users arrive, because Free's hard caps can make writes fail, and should move to Professional when call volume or the need for backups justifies a seat. Teams that price per seat elsewhere should model the per-developer fee early, since it is the line that grows fastest with headcount.

Convex is a weaker fit when your data is relational and you want SQL: Supabase and Neon give you Postgres you can dump and move. Mobile-first apps that lean on Google's analytics, messaging and crash reporting fit Firebase better, and the mobile backend ranking covers that case. For the wider field, see the best backend-as-a-service ranking and the Firebase alternatives list.