Featured Project

Sqlite Sync Pro

Sqlite Sync Pro is a synchronization library for applications that need local SQLite performance with remote PostgreSQL alignment, making offline-first desktop and mobile scenarios more realistic to build and support.

View on GitHub Back to Home

Overview

What it solves

Many real-world applications still need a local database for speed, resilience, and offline work. Sqlite Sync Pro is designed for that environment, giving applications a way to keep local SQLite data synchronized with a remote PostgreSQL service without giving up responsiveness or ownership of the local experience.

The library is especially relevant when teams need to bridge desktop or device-local workflows with cloud-hosted systems and user-level authentication.

It uses a background worker model, separate database access, and a push-pull sync engine to handle row serialization, transport, conflict handling, and pull tracking.

The result is an offline-first synchronization layer that can sit beneath products like Project Notes or other custom applications that need secure and practical data sync.

Cross-Platform Sync

From local database to shared project data

Sqlite Sync Pro supports the synchronization layer behind Project Notes, where local SQLite data can stay fast on each device while selected records move through a remote PostgreSQL/PostgREST host. These screens show the practical surfaces around that flow: host setup, user access, client settings, live sync stats, and cross-platform app use.

Sync network statistics on Windows showing upload and download activity by table. — **Bidirectional sync visibility** Upload and download activity is visible by cycle and by table, giving desktop applications a way to monitor what moved between local SQLite and the shared host.

Remote host user setup showing PostgreSQL sync users. — **Remote user provisioning** Sync users map to PostgreSQL roles so access can be managed outside the local app.

Project Notes sync settings on Linux for a self-hosted PostgREST server. — **Client-side sync settings** Each client can enable cloud sync, choose a host type, authenticate, and set an encryption phrase.

Remote host setup showing PostgreSQL and Supabase connection fields. — **Host configuration** Self-hosted and Supabase-style PostgreSQL targets can be configured through a guided setup flow.

Project Notes running on Linux in dark mode with project records. — **Linux desktop client** The same project data can be used from a native desktop interface in dark mode.

Project Notes running on macOS with project list data. — **macOS project workspace** Local-first records remain available in the full desktop project management experience.

Project Notes project list on iOS in dark mode. — **iOS mobility path** Mobile clients can participate in the same product data model for field and meeting workflows.

Capabilities

Core design themes

Bidirectional synchronization Background worker thread model Cross-platform desktop and mobile clients JWT-based authentication support Optional row encryption Schema inspection and JSON row transport Supabase and PostgREST-style deployment paths Qt test coverage with mock HTTP support Admin tooling and sample app patterns

Technical Story

How it is built

Public API plus worker loop

The public interface coordinates with a dedicated sync loop worker so applications can keep UI and local work responsive while synchronization happens in the background.

Schema-agnostic sync model

Local table rows are serialized into JSON payloads, allowing the remote side to store synchronized data in a flexible PostgreSQL model with row-level isolation.

Security-aware transport

Authentication, encryption, and remote-host configuration are treated as first-class concerns instead of being left as an application-specific afterthought.

Why it matters

Infrastructure for practical software

Sqlite Sync Pro is the kind of library that makes a larger product strategy possible. It enables applications to stay local-first and user-friendly while still participating in a connected architecture. For teams working in industrial, field, or hybrid environments, that tradeoff is often the difference between a concept that demos well and a tool that works in the real world.