// the take
PgStack turns Postgres logical replication into a managed pipeline that builds two separate read-only stores: a BM25/semantic search index (Lance) and a full row-change audit log (Iceberg/Parquet), both queryable through a Postgres-wire-compatible endpoint backed by embedded DuckDB. It's for teams who want full-text/semantic search or change auditing on their existing Postgres data without standing up Elasticsearch, Algolia, or hand-rolled trigger-based audit tables.
Wire-protocol compatibility means psql, existing ORMs, and BI tools hit it with zero new client code - that's a real integration win over bolting on a separate search engine. CDC via logical replication keeps indexing load off the OLTP database instead of running expensive queries against production. BM25/semantic/hybrid ranking as plain SQL functions (keyword_rank, semantic_rank, hybrid_rank) is a much lower-friction API than most search engines offer. Shipping as one container with NATS, DuckDB, Lance, and Iceberg all embedded makes local eval genuinely a one-command exercise.
The README says outright the bundled image is for local dev and evaluation only, with HA, autoscaling, and 'production security' reserved for the paid Cloud tier - so there's no real story for running this yourself in production, which undercuts the pitch for anyone who isn't going to pay. Semantic search is hard-wired to OpenAI's text-embedding-3-small with no pluggable provider, and a restart rebuilds the whole index and re-triggers embedding charges - that's a nasty surprise on any table of real size. The Postgres wire protocol support is implemented via a custom SQL parser and query remapper rather than genuine Postgres compatibility, so it only understands the subset of SQL it's been taught; expect query shapes that silently fail to remap correctly. AGPL-3.0 plus a clearly thinned-out OSS tier is standard open-core, and at 1500 stars with no indication of release cadence or how battle-tested the CDC path is under schema changes, it's still early for anything you can't afford to rebuild.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →