Databases · head to head
Convex vs Render

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

Render
Cloud
A modern cloud platform for the next generation
- From
- Free
- Free plan
- Yes
The short version
- Render is a unified platform to build and run all your apps and websites.
- Free plans on both; paid from $25/mo and $7/mo.
- Only Convex lists reactive queries; only Render lists web services.
- Where Render falls short: the free Hobby workspace is limited to 25 services and 5 GB of bandwidth.
- Prices and features on this page were last checked on 13 November 2026.
How do Convex and Render differ?
Convex and Render differ on pricing model (Subscription against Usage-based), platforms (Web against Web, API) and category (Databases against Cloud). Only the attributes on which Convex and Render actually diverge.
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Convex.
Which features does each one have?
They share no listed features; 10 appear only for Convex and 20 only for Render. 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 Render
- Web services
- Static sites
- Background workers
- Postgres database
- Redis database
- Scheduled jobs
- Environment variables
- Custom domains
What is each one used for?
Render is most often brought in for running managed Postgres and Redis alongside application services. 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 Render
- Agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cachenot Render
- Small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineersnot Render
- Prototypes that must become production without a rewrite of the data layer, where end-to-end TypeScript types remove a class of integration bugsnot Render
Render
- Deploying web services, static sites and cron jobs from a Git repository without managing serversnot Convex
- Running managed Postgres and Redis alongside application servicesnot Convex
- Preview environments per pull request for small teamsnot Convex
Where do Convex and Render fall short?
Render's most cited limit: the free Hobby workspace is limited to 25 services and 5 GB of bandwidth. 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
Render
- The free Hobby workspace is limited to 25 services and 5 GB of bandwidth
- Every paid plan charges the workspace fee plus compute on top, so $25 per month for Pro is a floor rather than a total
- SAML SSO and SCIM require the Scale plan at $499 per month
- HIPAA-compliant workspaces, inbound IP rules and advanced RBAC roles are Scale plan features
- Organization-level audit logs require Scale; Pro provides only workspace audit logs
- Contractual uptime SLAs, support response SLAs and a technical account manager are Enterprise only, and Enterprise is custom priced with no published rate
- Included bandwidth is 25 GB on Pro and 1 TB on Scale, with usage beyond that billed separately
How much do Convex and Render cost?
Convex has a free plan, with paid plans from $25/mo; Render has a free plan, with paid plans from $7/mo. 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
Render
Free- FreeFree
- 1 web service
- 1 static site
- Shared CPU
- Starter$7/mo
- Unlimited services
- Dedicated CPU
- 2GB RAM
Which should you pick?
Choose Convex if
- You need reactive queries.
- You want to start without paying.
- You also want typescript server functions.
Choose Render if
- You need web services.
- You want to start without paying.
- You work on Web, API.
- You also want static sites.
Questions people ask
- Is Convex or Render better?
- Neither clearly leads. Convex starts at Free and Render at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Convex or Render?
- Convex starts at Free and Render at Free.
- Does Convex or Render run on more platforms?
- Convex runs on Web. Render runs on Web, API.
- Can I use Convex for free?
- Both have a free tier, so you can try either at no cost before committing.
- 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 Render is typically brought in for.
- What can Convex do that Render cannot?
- Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database. Render covers Web services, Static sites, Background workers, Postgres database.
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.
Render: What is Render's pricing?
Render's pricing details are not disclosed on the public pricing page. The site references workspace plans, compute services, and features but does not display specific costs. Users must visit the pricing page directly or contact Render for detailed information.
SourceConvex: 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.
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.
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.
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.
Related pages
Other head to heads
- Convex vs Readyset
- Convex vs DynamoDB
- Convex vs FaunaDB
- Convex vs LanceDB
- Convex vs Xata
- Convex vs Materialize
- Convex vs BigQuery
- Convex vs dbt
- Convex vs OpenSearch
- Convex vs TiDB
- Convex vs Tinybird
- Convex vs Canary Labs
- Convex vs SQLite
- Convex vs StarRocks
- Convex vs Typesense
- Convex vs Apache Hadoop
- Convex vs Apache Solr
- Convex vs Valkey
- Convex vs Porter
- Convex vs Coolify
- Convex vs CapRover
- Convex vs Qovery
- Convex vs DigitalOcean
- Convex vs Dokku
- Convex vs Koyeb
- Convex vs Railway
- Convex vs Fly.io
- Convex vs Heroku
- Convex vs Northflank
- Convex vs SST
- Convex vs Proxmox VE
- Convex vs Rancher
- Convex vs Upstash
- Convex vs Lambda (AWS Serverless)
- Convex vs Buildah
- Convex vs CloudAMQP
- Render vs Readyset
- Render vs DynamoDB
- Render vs FaunaDB
- Render vs LanceDB
- Render vs Xata
- Render vs Materialize
- Render vs BigQuery
- Render vs dbt
- Render vs OpenSearch
- Render vs TiDB
- Render vs Tinybird
- Render vs Canary Labs
- Render vs SQLite
- Render vs StarRocks
- Render vs Typesense
- Render vs Apache Hadoop
- Render vs Apache Solr
- Render vs Valkey
- Render vs Porter
- Render vs Coolify
- Render vs CapRover
- Render vs Qovery
- Render vs DigitalOcean
- Render vs Dokku
- Render vs Koyeb
- Render vs Railway
- Render vs Fly.io
- Render vs Heroku
- Render vs Northflank
- Render vs SST
- Render vs Proxmox VE
- Render vs Rancher
- Render vs Upstash
- Render vs Lambda (AWS Serverless)
- Render vs Buildah
- Render vs CloudAMQP
