PowerSync Diagnostics App

PowerSync Diagnostics is a tool for monitoring the health of your PowerSync database sync.

  • Databases
  • Monitoring & Logging
PowerSync Diagnostics is a tool for monitoring the health of your PowerSync database sync. It identifies errors, tracks data flow, and keeps your data consistent between your server and client devices, helping you troubleshoot connection issues and confirm your system is running smoothly.

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
57742 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

GitHub stars
742
Open issues
43
Last commit
2026-11-18
Latest release
@powersync/[email protected]
License
Apache-2.0
Activity
steady

Checked 3 days ago - source: GitHub (powersync-ja/powersync-js)

Resources & Compatibility

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 for PowerSync Use Docker (a tool for running packaged programs) to start a Postgres database container, open port 5433 on your machine, and set a strong password. Then give a dedicated user permission to create tables in powersync_storage, because without that setup PowerSync has no storage and cannot keep sync data. source
  • Start PowerSync and create its database Use Docker Compose (the tool that starts a whole container stack) to start PowerSync, and create a powersync_storage database by connecting to Postgres on port 8090. Without that database, PowerSync has nowhere to store its bucket data. source
  • Check that PowerSync is ready After starting the service, run the startup check by requesting /probes/startup; a 200 response means PowerSync is ready, while a 400 means it is not started yet. This helps you know whether the app should connect or wait. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I connect the Diagnostics App to a self-hosted PowerSync service?

Connecting as a user requires a PowerSync Token, which is a JWT, and an Endpoint. For PowerSync development tokens, the endpoint is populated automatically from the JWT.

What should I use when a client has stopped syncing?

The Diagnostics App can be used to check sync conflicts or errors and collect logs.

What can the diagnostics client view or change?

It can view real-time sync status and bucket data, and manage client parameters.

What Postgres storage setup do the docs recommend for PowerSync?

Use Docker to start a Postgres container, open port 5433 on your machine, and set a strong password. Give a dedicated user permission to create tables in powersync_storage, because without that setup PowerSync has no storage and cannot keep sync data.

Answers sourced from diagnostics-app.powersync.com, docs.powersync.com, forums.justuseapp.com, hub.docker.com

Community

Collected 48 days ago - public community threads