Softwr

Databases · head to head

Convex vs Cyclr

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

Cyclr

Automation Integration

Embedded integration platform that SaaS vendors ship inside their own product

From
$1595/month
Free plan
No

The short version

  • Convex has a free plan, then $25/mo; Cyclr starts at $1595/mo.
  • Only Convex lists reactive queries; only Cyclr lists white-label integration UI.
  • Prices and features on this page were last checked on 13 November 2026.

How do Convex and Cyclr differ?

Convex and Cyclr differ on starting price (Free against $1595/month), pricing model and free tier (Yes against No). Only the attributes on which Convex and Cyclr actually diverge.

Attributes where Convex and Cyclr differ
AttributeConvexCyclr
Starting priceFree$1595/month
Pricing modelSubscriptionPer month by API call volume
Free tierYesNo
PlatformsWebWeb, API
CategoryDatabasesAutomation Integration

Which features does each one have?

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

  • White-label integration UI
  • Connector library
  • Workflow builder
  • Custom connectors
  • Regional hosting
  • MCP server offering
  • Usage metering
  • Templates

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

Cyclr

  • A mid-market SaaS vendor losing deals because prospects ask for a CRM integration it has not builtnot Convex
  • A product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectorsnot Convex
  • A European software company that needs its customers' integration data processed inside the EU for procurement reasonsnot Convex
  • A vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connectornot Convex

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

Cyclr

  • Entry pricing of 1,595 US dollars a month for one connector and 100,000 API calls means small vendors will find building two or three integrations in-house genuinely cheaper, and Cyclr only pays off past a certain integration count
  • Connectors and API calls are metered separately, so a successful integration marketplace pushes you up tiers as your customers adopt it, meaning the cost rises with usage rather than with the revenue that usage generates
  • Custom connectors to APIs outside the library are your work to build and maintain, so the promise of not building integrations only holds for applications Cyclr already covers
  • Debugging is harder when the integration runs in a third-party runtime, because your support team sees a failed workflow rather than an HTTP response and has to escalate to Cyclr for anything non-obvious
  • Deep embedding creates real switching cost: your customers' live integrations run on Cyclr, so migrating later means recreating every customer workflow, which in practice means you rarely leave

How much do Convex and Cyclr cost?

Convex has a free plan, with paid plans from $25/mo; Cyclr starts at $1595/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

Cyclr

$1595/month
  • PAYG$1,595/mo
    • 100,000 API calls included
    • 1 connector included
    • Unlimited integrations and users
  • Growth$2,595/mo
    • 1,000,000 API calls included
    • 10 connectors included
    • Everything in PAYG
  • Scale$7,195/mo
    • 5,000,000 API calls included
    • Unlimited connectors
    • Everything in Growth
  • Private CloudOn request
    • Dedicated hosting in US, UK or EU
    • Configurable processing and runtime
    • Quoted pricing

Which should you pick?

Choose Convex if

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

Choose Cyclr if

  • You need white-label integration ui.
  • You work on Web, API.
  • You also want connector library.

Questions people ask

Is Convex or Cyclr better?
Neither clearly leads. Convex starts at Free and Cyclr at $1595/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Convex or Cyclr?
Convex has a free tier; the other does not. Paid plans start at Free for Convex and $1595/month for Cyclr.
Does Convex or Cyclr run on more platforms?
Convex runs on Web. Cyclr runs on Web, API.
Can I use Convex for free?
Yes. Convex has a free tier, so you can try it without paying. Cyclr starts at $1595/month.
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 Cyclr is typically brought in for.
What can Convex do that Cyclr cannot?
Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database. Cyclr covers White-label integration UI, Connector library, Workflow builder, Custom connectors.

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.

Cyclr: What does Cyclr actually cost?

Published tiers start at 1,595 US dollars per month for 100,000 API calls and one connector, rising to 7,195 for unlimited connectors and five million calls.

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.

Cyclr: Do my customers know they are using Cyclr?

No. The interface is white-labelled to appear as part of your product.

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.

Cyclr: Can I host it in the EU or UK?

Yes, on the private cloud tiers, which matters for European procurement requirements.

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.

Cyclr: What if the connector I need does not exist?

You build a custom connector using Cyclr tooling, which is work you own rather than work the platform removes.

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