PowerSync

Sync engine for keeping backend databases in sync with in-app SQLite.

Postgres | MongoDB | MySQL | SQL Server

🐘🌿🐬🛢️«-» 🪶

[PowerSync @powersync_]

We did the same thing recently, migrated the powersync[dot]com website to Tanstack

Smooth sailing

[Warp @warpdotdev]

Our warp[dot]dev site gets 10M visitors/year. We migrated the whole thing from a no-code editor back to code in just 3 weeks.

Very few hiccups, and SEO actually improved. Plus, the marketing team is free to use Warp to ship future changes

[PowerSync @powersync_]

Kobie walks us through the new search functionality in the dashboard. Which features are we still missing?

[Kobie sync/acc @k081e]

PowerSync Dashboard quality of life addition: search your logs :)

[PowerSync @powersync_]

Full thread: https://t.co/5JeufdEJ48

[PowerSync @powersync_]

Evidence of how Sync Streams solve partial sync at scale - in this case a user is syncing 5B rows in their backend database to millions of rows in SQLite

[PowerSync @powersync_]

Self-managed Private Endpoints are now available:

- Connect your source database over private AWS networks
- Zero public internet exposure
- Fully self service - no need to contact support

https://t.co/UmpKjZxcuM

[PowerSync @powersync_]

More detail and link to the PoC:
https://t.co/YcOZe00RQq

[PowerSync @powersync_]

In this fun video, Steven shows us how he created an experimental @MikroORM integration.

For existing MikroORM users, PowerSync provides partial sync at scale: keep on-device SQLite synced with your backend database. PowerSync is designed for offline, real-time, and reactive use cases.

For existing PowerSync users, you might want to check out MikroORM as another great option. From what we can tell, the latest version probably works on React Native and Web too.

[PowerSync @powersync_]

Repo: https://t.co/icR6OmcwlF

The specific example is for React Native, but the approach generalizes to any of our supported SDKs

[PowerSync @powersync_]

We often speak to customers that are syncing massive (1GB+) volumes into SQLite

This is something we'll have better support for over time, but a good workaround for now is to use the PowerSync SQLite Seeder community project

[PowerSync @powersync_]

https://t.co/8azeqFLIQi

[PowerSync @powersync_]

Partial, consistent sync at scale is one of the hardest problems solved by PowerSync.

We first launched with a declarative system called Sync Rules, which synced a user’s entire dataset to their device on first connect.

This fell short in use cases where you didn't want to or need to sync everything up-front. So we built Sync Streams: a system where clients can still sync everything up front, or subscribe lazily to exactly what they need, when they need it, using parameters.

Sync Streams has been soaking in the wild for the past few months and is now GA / Stable. Thanks to everyone who helped us put it through its paces.

[PowerSync @powersync_]

Using our reactive watch queries, you don't need to build UI invalidation by hand. Available on all our SDKs.

Great article by @InfoWorld promoting sync as a paradigm

[InfoWorld @InfoWorld]

Kill the loading spinner with local-first data and reactive SQL
https://t.co/jwqDw03Uws

[PowerSync @powersync_]

"Local-first is not offline-first."

This is a clear take on why the distinction matters, and includes a kind nod 🥰

[Smashing Magazine 🇺🇦 🏳️‍🌈 @smashingmag]

✨ What does it really take to build local-first web apps in 2026? A grounded, experience-driven perspective for developers who’ve been doing this long enough to be skeptical of silver bullets: https://t.co/KUr2Jzqp8c

[PowerSync @powersync_]

@rodydavis 👍
What's your sentiment on the overall stability of OPFS in Chrome?

[PowerSync @powersync_]

Persistence on the web in prod?

[PowerSync @powersync_]

Full discussion - https://t.co/NXmzlrg6vp

[PowerSync @powersync_]

The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!

It does this by not insisting every commit hit the disk immediately. Instead of updating the main database file right away, it writes changes into side log files first. That is cheaper, so small write transactions finish much faster.

[PowerSync @powersync_]

If the app needs stronger guarantees, it can turn durability back up with PRAGMA synchronous=FULL or EXTRA. Then the VFS flushes more aggressively so recent commits are much more likely to survive crashes, but write performance drops. In plain English: NORMAL/OFF = faster but may lose latest writes; FULL/EXTRA = safer but slower.