PowerSync

PowerSync synchronizes selected backend data to client SQLite. The application still owns authentication, its mutation backend, validation, authorization, conflict policy, and source-database integrity.¹²³⁵⁶

For: Web and mobile teams that need responsive local reads and writes through intermittent or absent connectivity

• Offline writes are not actually required and a simpler read-path or online architecture is sufficient.
• The authoritative database, client platform, Sync Stream semantics, or feature maturity does not fit.
• Conflict, rejection, authorization, revocation, or recovery behavior cannot be made safe for the domain.
• Cloud data volume and concurrency or self-hosted reliability costs exceed the product value.

• Client-local SQLiteAuthorized data is materialized into a standard SQLite database for fast local queries and reactive application state.¹²
• Offline-capable flowReads and locally queued mutations can continue through interrupted connectivity when the application write path is designed for it.¹²
• Selective synchronizationCurrent Sync Streams define parameterized subsets and subscriptions; legacy Sync Rules remain supported for existing projects.²
• Deployment choicePowerSync documents managed Cloud, free source-available Open Edition, and commercial Enterprise Self-Hosted routes.³⁵⁶

PowerSync Cloud combines plan fees with organization-wide quotas and overages for data synced, hosted data, and peak concurrent connections. The free source-available Open Edition shifts infrastructure and operations to the team, while Enterprise Self-Hosted uses custom commercial terms.⁵

Cloud plans

Free, Pro, Team, and Enterprise with organization-level usage aggregation⁵

Primary Cloud meters

Data synced to clients, data hosted by PowerSync, and peak concurrent connections⁵

Self-host boundary

Free source-available Open Edition or commercial Enterprise Self-Hosted plus infrastructure and operations⁵