What meets the eye
What lurks beneath
Connect PowerSync to your SQL database and existing backend API. No SQL write permission required. The PowerSync SDK sends writes back to your backend API, allowing you to keep using the business logic in your existing backend application.
Example showing PostgreSQL config file
Example showing Amazon RDS
After setting PowerSync up for dev mode, you can follow these steps to set it up for production:
1. Add authentication
In your backend, add an endpoint to generate PowerSync JWT tokens. In your app, use this endpoint to get an JWT authentication token.
2. Add custom write APIs
In your backend, add endpoints to write data (or use existing ones). In your app, hook up these endpoints.
3. Add sync rules on PowerSync dashboard
4. Configure client-side schema
Start with auto-generated schema on the PowerSync dashboard (generated from your SQL database), then customize as needed. Add this to your app.
5. Disable dev mode
Query SQLite directly, or use built-in ORM
Use whatever works best for you. By default, the SQLite schema matches your PostgreSQL schema.
Data filtering with sync rules
Define sync rules to filter and route data so users only see data that's relevant to them.
Supports custom conflict resolution
Because all writes go through your backend API, you can easily add custom conflict resolution logic.
Super fast SQLite performance
The PowerSync SDK includes several optimizations that result in incredibly fast database queries and writes.
SDK is implemented in a NoSQL-like way
Client-side schema and data migrations are not necessary. Schema changes require reprocessing of sync tables. A resync may be required on the client side which is handled automatically.
Multiple databases, one cloud service
Multiple source databases can be connected to one instance of the PowerSync cloud Service.