PowerSync Service
PowerSync Service is a backend service that keeps client-side SQLite databases in sync with your backend database, enabling mobile and web apps to work offline.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
75/100 Good
- Maintained
- 100last commit 3 days ago
- Popular
- 52406 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 801 GB minimum RAM, runs on ARM
- Security check
- 100no serious findings, CI, tests
- GitHub stars
- 406
- Open issues
- 34
- Last commit
- 2026-11-18
- Latest release
- v1.29.1
- License
- Apache-2.0
- Activity
- rising
Checked 2 days ago - source: GitHub (powersync-ja/powersync-service)
Resources & Compatibility
Minimum requirements: 1 GB RAM, 1 CPU core(s). ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set up Postgres storage first Start a Postgres (PostgreSQL) storage container for PowerSync, choose a strong password, and create a dedicated storage user with permission to create things in the powersync_storage database. PowerSync uses this database to store sync data, so missing or under-privileged storage setup can stop it from saving data. source
- Keep the storage port reachable Leave the local port mapping for storage (the way your machine connects to the database), such as -p 5433:5432, so PowerSync can reach it at 127.0.0.1:5433. If that port is closed or blocked, the service may not be able to read or write sync data. source
- Check the service is ready before use After the service is running, check the startup status URL, such as GET /probes/startup, and look for a 200 response. If it returns 400, PowerSync has not finished starting, so wait before letting clients connect. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What Postgres storage setup is needed for PowerSync Service?
Start a Postgres storage container, choose a strong password, and create a dedicated storage user with permission to create things in the powersync_storage database. PowerSync uses this database to store sync data.
Which storage port must remain reachable in a local Docker setup?
Keep the local port mapping for storage open, such as mapping 5433 to the database port, so PowerSync can reach it at 127.0.0.1:5433. If the port is closed or blocked, the service may not be able to read or write sync data.
Where should the self-hosted sync config be mounted?
The demos explicitly mount a local powersync folder at /config inside the PowerSync container. Each demo keeps its own sync config there so it can be understood and changed independently.
Can I use the PowerSync CLI with an instance I did not create with the CLI?
Yes, CLI commands such as status, validate, generate schema, and generate token work alongside any running self-hosted instance. You do not need to have set up the instance with the CLI.
Answers sourced from docs.powersync.com, docs.powersync.com, github.com
Community
- Reddit (reddit)
Collected 48 days ago - public community threads