Softwr

Databases · head to head

ArangoDB vs Convex

ArangoDB logo

ArangoDB

Databases

Multi-model database for graph, document, and search

From
Free
Rated
-
Full reviewWebsite
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
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: ArangoDB the company has repositioned around a wider platform, so ArangoDB is now described as the foundation inside Arango rather than the product itself; 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.
  • They diverge on capability: ArangoDB covers Multi-model Support, Convex covers Reactive queries.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which ArangoDB and Convex actually diverge.

Attributes where ArangoDB and Convex differ
AttributeArangoDBConvex
Pricing modelfreemiumsubscription
PlatformsLinux, Windows, Mac, Docker, WebWeb
Founded2014Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

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 ArangoDB

  • Multi-model Support
  • AQL Query Language
  • Graph Traversals
  • Full-text Search
  • ACID Transactions
  • SmartGraphs
  • Satellite Collections
  • Foxx Microservices

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

What people use each for

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

ArangoDB

  • Graph, document and key-value data in one databasenot Convex
  • Vector and full-text search alongside graph traversalnot Convex
  • Avoiding separate stores for related and unstructured datanot Convex
  • Backing AI applications needing both graph context and vectorsnot Convex

Convex

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

Where each one falls short

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

ArangoDB

  • The company has repositioned around a wider platform, so ArangoDB is now described as the foundation inside Arango rather than the product itself
  • Neither the community licence terms nor cloud pricing are stated on the main site
  • arangodb.com redirects to arango.ai

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.

Pricing, plan by plan

ArangoDB

Free
  • CommunityFree
    • All data models
    • AQL queries
    • Full-text search
  • ArangoGraph$99/month
    • Managed service
    • Graph analytics
    • Enterprise support

Convex

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

Which should you pick?

Choose ArangoDB if

  • You need multi-model support.
  • You want to start without paying.
  • You work on Linux, Windows, Mac, Docker, Web.
  • You also want aql query language.
ArangoDB review

Choose Convex if

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

Questions people ask

Is ArangoDB or Convex better?
Neither clearly leads. ArangoDB starts at Free and Convex at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, ArangoDB or Convex?
ArangoDB starts at Free and Convex at Free.
Does ArangoDB or Convex run on more platforms?
ArangoDB runs on Linux, Windows, Mac, Docker, Web. Convex runs on Web.
Can I use ArangoDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is ArangoDB best used for?
ArangoDB is most often used for graph, document and key-value data in one database, vector and full-text search alongside graph traversal, avoiding separate stores for related and unstructured data, backing ai applications needing both graph context and vectors. Of those, graph, document and key-value data in one database and vector and full-text search alongside graph traversal are not what Convex is typically brought in for.
What can ArangoDB do that Convex cannot?
ArangoDB covers Multi-model Support, AQL Query Language, Graph Traversals, Full-text Search. Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database.

Answered from the vendors’ own pages

ArangoDB: How is ArangoDB priced?

ArangoDB offers Community Edition (free) and Enterprise Edition. Pricing is customized based on deployment model (self-managed, managed cloud AWS/GCP, or OEM/embedded) and customer requirements. Contact Arango for a quote.

Source
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.

ArangoDB: What deployment options does ArangoDB offer?

ArangoDB can be deployed self-managed on customer infrastructure, as managed cloud (Arango Managed Platform on AWS/GCP), or as OEM/embedded solutions.

Source
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.

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.

Share

Related pages

More on ArangoDB

More on Convex

Keep looking

Other head to heads