
@powersync_i
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
Sync engine for keeping backend databases in sync with client-side SQLite. Postgres | MongoDB | MySQL | SQL Server | Azure DocumentDB ššæš¬š¢ļøĀ«-Ā» šŖ¶
Distributed
Joined May 2023
- Tweets1.6K
- Following786
- Followers2.2K
- Likes1.6K
2026 is still shaping up to be the year of the sync engine, just like @dexhorthy predicted!
smry.ai represents a new class of web app where the benefits of sync on the web can be aligned with user ownership of data, and easy for agents to build into your app.
letās talk about sync
ever since watching theoās videos about t3 chat local sync, I wanted it for smry.ai
but as I worked on it, I realized itās not a good-to-have, itās a must-have for a reading assistant, as your reading history needs to load instantly.
also users want to own their data, which they do if itās cached on their own browser
i evaluated every provider: zero/electric/etc, even built my own shitty one!
but nothing was as good as powersync, which is super cheap, scales like crazy, has a drizzle integration, and has a team with actual support (also everyone else in the space seems to die/get bought)
powersync was the best solution for sync, but really the team was the best part
iām able to work much faster now that Iām not worried about hand-rolled sync breaking with every change, and with all code written by agents itās good to have a tool that has the things they need to succeed
Michael's search for a good sync solution has ended.
smry.ai is now running on @powersync_
read about his journey: powersync.com/blog/how-smry-ā¦
We've published a blog post with more details
powersync.com/blog/emudhra-sā¦
We've released 1.27.1 of the PowerSync Service on Docker Hub. It contains mitigations for the eMudhra Intermediate CA Compromise.
The compromise could affect JWKS fetching and TLS connections for source databases. It is recommended to upgrade now.
github.com/powersync-ja/poweā¦
We've released 1.27.1 of the PowerSync Service on Docker Hub. It contains mitigations for the eMudhra Intermediate CA Compromise.
The compromise could affect JWKS fetching and TLS connections for source databases. It is recommended to upgrade now.
github.com/powersync-ja/poweā¦
PowerSync DevTools have shipped - inspect your app's live database
Our team couldn't resist memeing a video about this one š
releases.powersync.com/annouā¦
We were approached by @Microsoft to add support for @DocumentDB as a source database for PowerSync.
It has been a pleasure working with their team to get this shipped, and they blogged about some of the capabilities and use cases:
devblogs.microsoft.com/documā¦
The PowerSync CLI now has a --dry-run flag for all deploy commands, to review changes before deploying. If you're paranoid about agents running amok, this could help.
Available in v0.10.2
Sometimes your app requires fast user switching. If you call disconnectAndClear(), then each time a user switches they need to re-download all their data.
To make user switching faster, consider preserving local data when disconnecting: db.disconnectAndClear({ soft: true })
The integration creates a dedicated replication role, presents a small UI to select tables to replicate&sync, and automatically configures PowerSync's db connection to Supabase, and configures PoweSync to use Supabase auth when authenticating clients.





