What's changing: Convex (an open-source backend-as-a-service platform) has been added as a new replication source module for the PowerSync Service. Users can point the service at a Convex backend — self-hosted or Convex Cloud — and sync data to client SDKs via PowerSync's sync engine. The integration has notable constraints documented in the module README, particularly around mutation transaction atomicity.
Why this matters for docs: New third-party integration — a new source database/backend that users must configure end-to-end before sync works.
Likely affected pages/sections:
- New page needed — "Convex" source database setup guide (parallel to existing PostgreSQL, MySQL, MongoDB, MS SQL Server pages): connection configuration, required Convex schema setup (
powersync_checkpoints table + write mutation function), transaction atomicity caveats, self-host vs Convex Cloud differences.
- Supported source databases overview / introduction — add Convex to the list of supported replication sources.
- Self-hosting / configuration reference — document the Convex replicator module configuration block in
service.yaml.
Note: A draft docs PR is already in progress at #456. This issue is filed to ensure the work is tracked in the standard drift queue.
Source PR: powersync-ja/powersync-service#574. Note: at the time of filing this issue the PR is open. Publish updates only after the PR is merged and the change shipped in a release.
Filed automatically by a scheduled process running on Claude Code (claude-sonnet-4-6). A human should verify the scope and timing before publishing any changes.
What's changing: Convex (an open-source backend-as-a-service platform) has been added as a new replication source module for the PowerSync Service. Users can point the service at a Convex backend — self-hosted or Convex Cloud — and sync data to client SDKs via PowerSync's sync engine. The integration has notable constraints documented in the module README, particularly around mutation transaction atomicity.
Why this matters for docs: New third-party integration — a new source database/backend that users must configure end-to-end before sync works.
Likely affected pages/sections:
powersync_checkpointstable + write mutation function), transaction atomicity caveats, self-host vs Convex Cloud differences.service.yaml.Source PR: powersync-ja/powersync-service#574. Note: at the time of filing this issue the PR is open. Publish updates only after the PR is merged and the change shipped in a release.
Filed automatically by a scheduled process running on Claude Code (claude-sonnet-4-6). A human should verify the scope and timing before publishing any changes.