Enforce Access Policies on Postgres

Scale PostgreSQL without changing your app

We built InsForge because we wanted to use pure prompts to build a production-grade app faster. In practice, AI isn’t reliable enough when generating code or configuring backend pieces like schema, RLS, auth, or functions. Postgres MCP and Supabase MCP are a good starting point, but they felt more like API wrappers for agents than something designed to guide AI safely through backend tasks. So we built our own MCP server on top of Postgres and added a set of context-engineering tools to make prompt-driven workflows more predictable. It gradually turned into a Postgres-based BaaS. Key…

hey hn, supabase ceo here this is a postgres connection pooler. it’s similar to pgbouncer, but built with Elixir and specifically designed for multi-tenancy. it’s still under development, but it’s at a stage where we can gather a feedback from the community and you can try it yourself. we aren’t using this in production yet, but aiming to deploy it for a subset of databases in the next 2 months. We have the following benchmarks (details in the readme): - Elixir Cluster maintaining 400 connections to a single Postgres database - 1_000_000 clients connecting to the Elixir cluster - Sending…

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…

In-memory Postgres for unit/E2E tests. Contribute to hexclave/pgmock development by creating an account on GitHub.

It's time we talked about something many developers, data analysts, and even web application servers are guilty of: downgrading PostgreSQL connection security. Too often, we see connections dropped from full TLS verification to "any TLS" (i.e., sslmode=require) or, even worse, plain text connections. Why? Because most cloud providers, like AWS or Google Cloud SQL, use non-public Certificate Authorities for PostgreSQL. The result? Unverified TLS connections because no one has time to set up all devices across an organization to trust custom certificate authorities. And here's the most…