zknill/sqledge

Health v2 · maintenance only

Flags: no_releases no_license

Adoption not part of the score

1043 stars · 20 forks observed · 2026-10-05

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

SQLedge replicates a Postgres database to a local SQLite file using Postgres logical replication, serving reads from SQLite while forwarding writes to upstream Postgres. It includes a Postgres wire-protocol proxy so applications can connect as if to Postgres and get fast, eventually consistent local reads.

Use cases

• run read-heavy apps at the edge with local SQLite reads
• replicate postgres to sqlite for fast local queries
• serve reads locally while writing to a central postgres
• proxy postgres wire protocol with sqlite-backed reads
• eventually consistent read replica on the edge
• stream postgres changes into an embedded sqlite database

When to choose

• your workload is read-heavy and can tolerate eventual consistency
• you want low-latency local reads close to your app
• your read queries are simple SELECTs compatible with SQLite syntax
• you want a lightweight read replica without running a full Postgres instance

When to avoid

• you need Postgres-specific SQL functions or syntax in read queries
• you require strong consistency between reads and writes
• you need a production-stable, well-supported solution (project is alpha with no license)
• your schema relies on Postgres features SQLite lacks, like complex types or extensions

Facets

service · maturity experimental

database streaming proxy http-server databases microservices backend developer-tools go self-hosted postgres sqlite logical-replication edge-computing read-replica wire-protocol linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="zknill/sqledge")