Avoid the complexities of using APIs to move app state over the network. Get super-fast, always-available offline-first/local-first apps.
PowerSync connects to your MongoDB database with only the limited permissions needed.
PowerSync automatically handles changes in document structure and JSON Schema with no need for client-side migrations.
The PowerSync Service uses change streams with post-images to detect insert, update and delete operations on documents.
The PowerSync Service tracks changes to data in the buckets, allowing for efficient delta syncing to clients.
You define Sync Rules which determine which data is synced to which users. Data is grouped into buckets which can be shared between users to avoid duplication.
Clients authenticate against the PowerSync Service using JWTs.
The client SDK initially downloads all relevant data and then incrementally keeps it updated, in real time.
Writes are immediately applied locally, and queued for upload to your backend API. The PowerSync client SDK automatically handles failures and retries.
On the client, data is persisted to a SQLite database in schemaless format. The application defines a client-side schema which is applied as SQLite views.
Live reactive queries can be used to update the UI when data changes.
PowerSync uses a server-authoritative architecture with a checkpoint system to guarantee consistency.
Your backend accepts uploaded writes and then applies them to your Postgres database.
PowerSync connects to your MongoDB database with only the limited permissions needed.
PowerSync automatically handles changes in document structure and JSON Schema with no need for client-side migrations.
The PowerSync Service uses change streams using post-images to get the complete document after each change.
Sync Rules determine which data is replicated and how it should be grouped into buckets for syncing to clients.
The PowerSync Service tracks changes to data in the buckets, allowing for efficient delta syncing to clients.
Your backend accepts uploaded writes and then applies them to your Postgres database.
Clients authenticate against the PowerSync Service using JWTs.
The client SDK initially downloads all relevant data and then incrementally keeps it updated, in real time.
On the client, data is persisted to a SQLite database in schemaless format. The application defines a client-side schema which is applied as SQLite views.
Writes are immediately applied locally, and queued for upload to your backend API. The PowerSync client SDK automatically handles failures and retries.
Live reactive queries can be used to update the UI when data changes.
PowerSync uses a server-authoritative architecture with a checkpoint system to guarantee consistency.