nowfound

Alternatives

Products that do what pgfence does

Stop dangerous Postgres migrations before hitting production

  1. 1PS

    Hey HN! Lev and Justin here, authors of PgDog (https://pgdog.dev/), a connection pooler, load balancer and database sharder for PostgreSQL. If you build apps with a lot of traffic, you know the first thing to break is the database. We are solving this with a network proxy that works without requiring application code changes or database migrations. Our post from last year: https://news.ycombinator.com/item?id=44099187 The most important update: we are in production. Sharding is used a lot, with direct-to-shard queries (one shard per query) working pretty much…

    Feb 2026 · github.com

  2. 2
    Warestack444

    Agentic guardrails for safe releases

    2025

  3. 3ZD
  4. 4PN

    pg_netstat is a Postgres extension to monitor database network traffic. It uses libpcap to capture packets and aggregates at user-specified interval.

    2022 · github.com

  5. 5
    Opengrep340

    The open source code security engine

    2025

  6. 6PS

    Hey HN! Lev here, author of PgDog (https://github.com/pgdogdev/pgdog). I’m scaling our favorite database, PostgreSQL. PgDog is a new open source proxy, written in Rust, with first-class support for sharding — without changes to your app or needing database extensions. Here’s a walkthrough of how it works: https://www.youtube.com/watch?v=y6sebczWZ-c Running Postgres at scale is hard. Eventually, one primary isn’t enough at which point you need to split it up. Since there is currently no good tooling out there to do this, teams end up breaking their apps…

    2025 · github.com

  7. 7
    Warestack437

    Enforce DevOps best practices today

    2024

  8. 8PE

    2018 · bluejekyll.github.io

  9. 9PT

    PgQueuer is a minimalist, high-performance job queue library for Python, leveraging the robustness of PostgreSQL. Designed for simplicity and efficiency, PgQueuer uses PostgreSQL's LISTEN/NOTIFY to manage job queues effortlessly.

    2024 · github.com

  10. 10
    Subtrace303

    Resolve production issues faster

    2025

  11. 11PR
  12. 12DG
  13. 13PC

    Hello HN! Keeping Elasticsearch or Algolia in sync with Postgres is a pain when your data spans multiple tables. Traditional CDC tools like Debezium capture table-level events but don’t help when you need to index a full entity composed of related records. That's why I built PG-Capture. PG-Capture lets you define a schema as complex as you need, aggregate table-level events, and reconstruct structured objects spanning multiple tables. It then publishes them as meaningful domain-level events to any queue (RabbitMQ, SQS, etc.). PG-Capture does NOT replace Debezium, it works on top of it (or…

    2025 · pg-capture.onrender.com

  14. 14PM
  15. 15SP

    This is a MVP for Serverless Postgres. 1/ It uses Fly.io[0], which can automatically pause your database after all connections are released (and start it again when new connections join). 2/ It uses Oriole[1], a Postgres extension with experimental support for S3 / Decoupled Storage[2]. 3/ It uses Tigris[3], Globally Distributed S3-Compatible Object Storage. Oriole will automatically backup the data to Tigris using background workers. I wouldn't recommend using this in production, but I think it's in a good spot to provoke some discussion and ideas. You can get it running…

    2024 · github.com

  16. 16

    Connect your data to your agents.

    Feb 2026

  17. 17PC
  18. 18PA
  19. 19
    Myriade101

    Ask your data. See the SQL. Self-host in one command.

    2025

  20. 20SD

    Hi HN, we're excited to share our open source tool with the community! We previously posted here with the tagline “real-time events for Postgres” [0]. But after feedback from early users and the community, we’ve shifted our focus to working on tooling for manual database changes. We've consistently heard teams describe challenges with the way manual data updates are handled. Seemingly every engineer we spoke with had examples of errant queries that ended up causing significant harm in production environments (data loss/service interruptions). We’ve seen a few different approaches to how…

    2023 · github.com

  21. 21PA
  22. 22PF

    Hi HN! My name is Sven, I am an engineer at Timescale and this is my fun side project. The main purpose of pgspot is to check postgres extension sql scripts for vulnerabilities but it can also be used to check functions outside of extension context e.g. security definer functions. I've started working on this after finding vulnerabilities in timescaledb to ensure similar vulnerabilities don't reappear. While working on this i found vulnerabilities in over 30 extensions and some of the findings even lead to postgres upstream changes to reduce attack surface of extension scripts (…

    2024 · github.com

  23. 23PP
  24. 24SF

Ranked by how close each launch is in meaning, then by votes. Refine with a description →