Feature Requests

This feature will allow configuring Custom Roles to only have access to specific components, instead of to all data in the entire application

This feature will allow configuring granular usage limits for individual deployments. e.g. "Allow 50 GB of DB I/O per month"

Add support for teams to automatically add and remove Convex team members with a pre-assigned role with SCIM

For business customers, paused/unpaused deployments have the same overhead cost. Lower cost of paused deployments to enable teams with large numbers of idle deployments (eg app builders).

Public deployment APIs for continuous streaming export of data.

Allow components to define "use node" actions.

Convex currently enforces its own _id primary key for all tables which is problematic and sub-optimal performance-wise in various use cases: Migrating data from previous databases to preserve primary keys/relationships Using 3rd parties as the source of truth for primary keys e.g. Clerk users, orgs,…

Provide caching at the "sub query" level inside the convex deployment. Specifically if a developer calls ctx.runQuery(...) within a query or mutation, and that individual query's cache value is still valid, the cached value will be used instead of running v8 again. This will allow developers to cont…

To better handle background jobs

Convex cloud provides global edge caches that serve cached queries at low latency everywhere on earth.

Allow Convex deployments to be provisioned in Canada.

Support inexpensive copy-on-write database clones so teams can create realistic test environments and reproduce bugs without paying full storage costs each time.

Improve analytical workloads with better support for reporting, aggregations, warehouse-style queries, and downstream BI integrations without compromising transactional workloads.

Ship a second-generation auth stack with cleaner primitives, better provider ergonomics, and smoother migration paths for apps already running in production.