Softwr

Databases · head to head

Convex vs Decodable

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
Decodable logo

Decodable

Automation Integration

Managed Apache Flink and Debezium with credit-based pricing and a free tier

From
Free
Free plan
Yes

The short version

  • Decodable is free; Convex starts at $25/mo.
  • Only Convex lists reactive queries; only Decodable lists managed Flink.
  • Where Decodable falls short: the free tier retains streams for only 24 hours, which is too short to debug an intermittent failure that surfaces days later.
  • Prices and features on this page were last checked on 13 November 2026.

How do Convex and Decodable differ?

Convex and Decodable differ on pricing model, platforms (Web against Web, Linux) and category. Only the attributes on which Convex and Decodable actually diverge.

Attributes where Convex and Decodable differ
AttributeConvexDecodable
Pricing modelSubscriptionPer credit by task hour
PlatformsWebWeb, Linux
CategoryDatabasesAutomation Integration

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

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

  • Managed Flink
  • Change data capture
  • SQL pipelines
  • Custom Flink jobs
  • Credit-based metering
  • Managed connectors

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 Decodable
  • Agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cachenot Decodable
  • Small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineersnot Decodable
  • Prototypes that must become production without a rewrite of the data layer, where end-to-end TypeScript types remove a class of integration bugsnot Decodable

Decodable

  • Streaming Postgres change data capture into Snowflake or Iceberg without running Debezium and Kafka Connect yourselfnot Convex
  • Real-time enrichment and filtering of event streams before they reach an expensive warehousenot Convex
  • A team that already writes Flink jobs but does not want to operate the cluster, checkpoint store or upgradesnot Convex
  • Replacing a fragile set of cron jobs and Lambda functions that move data between operational systemsnot Convex

Where do Convex and Decodable 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

Decodable

  • Credit pricing rewards intermittent work and penalises always-on pipelines: a single small task running continuously costs roughly 86 US dollars a month before any parallelism
  • Parallelism multiplies tasks, so scaling a pipeline to keep up with throughput multiplies the bill in a way that is easy to under-forecast at design time
  • The free tier retains streams for only 24 hours, which is too short to debug an intermittent failure that surfaces days later
  • Java and Python transformations are gated behind paid plans, so anything the SQL layer cannot express means moving off the free tier immediately
  • The operational layer is proprietary even though Flink and Debezium are not, so migrating to self-managed Flink later means rebuilding connectors, schema handling and monitoring from scratch

How much do Convex and Decodable cost?

Convex has a free plan, with paid plans from $25/mo; Decodable is free to use. 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

Decodable

Free
  • FreeFree
    • Up to four concurrent tasks
    • Small and medium task sizes
    • 24 hour or 10 GB stream retention
  • On DemandOn request
    • 0.12 USD per credit, billed monthly
    • Unlimited concurrent tasks
    • Small, medium and large task sizes
  • EnterpriseOn request
    • 0.10 USD per credit on pre-purchased annual capacity
    • Custom task sizes
    • Extensible retention

Which should you pick?

Choose Convex if

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

Choose Decodable if

  • You need managed flink.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want change data capture.

Questions people ask

Is Convex or Decodable better?
Neither clearly leads. Convex starts at Free and Decodable at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Convex or Decodable?
Convex starts at Free and Decodable at Free.
Does Convex or Decodable run on more platforms?
Convex runs on Web. Decodable runs on Web, Linux.
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 Decodable is typically brought in for.
What can Convex do that Decodable cannot?
Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database. Decodable covers Managed Flink, Change data capture, SQL pipelines, Custom Flink jobs.

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.

Decodable: What is a credit worth?

0.12 US dollars on On Demand and 0.10 on Enterprise. A small task consumes one credit per hour, medium two, large four.

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.

Decodable: Is there a free plan?

Yes, up to four concurrent tasks with 24 hour or 10 GB stream retention.

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.

Decodable: Is it really Apache Flink underneath?

Yes, Flink for processing and Debezium for change data capture, both managed by Decodable.

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.

Decodable: Can I run my own Flink jobs?

Yes, Java and Python jobs on paid plans; the free plan is SQL only.

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