Launching today
pgSentry
PostgreSQL-only. The micro-DBA for modern engineering teams
1 follower
PostgreSQL-only. The micro-DBA for modern engineering teams
1 follower
Postgres often fails silently (bloat, replication lag/WAL growth, inactive replication slots, slow query regressions, blocking locks). pgSentry watches your DB and turns those signals into a clear dashboard + severity-ranked, actionable recommendations (with copy-paste SQL fixes) — before they become incidents. Works with AWS RDS, Supabase, Neon, Google Cloud SQL, and self-hosted.
I’m building pgSentry, a PostgreSQL micro-DBA designed for teams that don’t have a dedicated DBA (or engineers who want quicker, clearer DB visibility).
You connect your Postgres cluster using a read-only user, and pgSentry will automatically analyze key health areas like tables, indexes, bloat/vacuum signals, replication lag/WAL/slots, locks, and slow query patterns, then suggest improvements with actionable recommendations. I’m also planning a feature where you can paste a slow query and get a breakdown of likely bottlenecks and what to check next.
I’ve just launched an early beta and my goal right now is to learn from Postgres experts and practitioners:
What features would bring the most daily value for you? What should I prioritize first to solve real production pain and automate the small but important DBA tasks?
If you’re open to it, I’d love your feedback (and you can try the beta here): https://pgsentry.com/
Looking forward to your thoughts 🙌