Introducing pgpulse: Observability for Supabase
We're excited to launch pgpulse, a new observability platform designed specifically for Supabase projects. Real-time monitoring, intelligent alerts, and database advisory—all without the complexity of traditional tools.
Today, we’re thrilled to announce pgpulse, a purpose-built observability platform for Supabase projects. If you’ve ever struggled with setting up Grafana dashboards, configuring Prometheus exporters, or piecing together monitoring for your Supabase infrastructure, pgpulse is for you.
Why We Built pgpulse
As Supabase adoption grows, teams are running increasingly mission-critical workloads. But setting up proper observability remains challenging:
- Complex setup: Traditional tools like Grafana require significant configuration
- Generic dashboards: Off-the-shelf solutions don’t understand Supabase-specific metrics
- Alert fatigue: Configuring meaningful alerts requires deep PostgreSQL expertise
- Fragmented tools: Monitoring, alerting, and database optimization are separate systems
We built pgpulse to solve these problems with a Supabase-native approach.
Core Features
📊 Supabase-Native Monitoring
pgpulse connects directly to your Supabase project’s metrics endpoint. No agents, no sidecars, no infrastructure to maintain. You get pre-configured dashboards showing:
// Metrics we track automatically
const metrics = {
connections: 'Active database connections',
latency: 'API response time (p50, p95, p99)',
errors: 'Error rates across endpoints',
storage: 'Database size and growth trends',
};
🚨 Intelligent Alerts
Create threshold-based alerts in seconds. Route notifications to Slack, webhooks, or email:
- DB connections > 80% for 5 minutes → Alert DevOps
- API latency p95 > 200ms → Notify on-call
- Error rate spike → Immediate escalation
🔍 Database Advisory
Our advisory engine runs automated health checks on your database:
- Missing indexes on frequently queried columns
- Table bloat from unvacuumed data
- Long-running queries consuming resources
- Connection pool exhaustion patterns
Each advisory comes with ready-to-run SQL to fix the issue—or you can promote it to an ongoing alert.
Getting Started
Getting pgpulse running takes less than 5 minutes:
- Connect your Supabase project — Provide your project URL and service key
- Configure alerts — Set thresholds for the metrics that matter to you
- Invite your team — Share dashboards and route alerts to the right channels
Try pgpulse free for 14 days at pgpulse.io.
What’s Next
We’re just getting started. On our roadmap:
- Query performance analysis — Identify slow queries with execution plan visualization
- Cost optimization — Recommendations to reduce your Supabase bill
- Incident timelines — Correlate alerts with deployments and changes
- Multi-region support — Monitor Supabase projects across different regions
We’d love to hear your feedback. Join our Discord community or reach out at admin@pgpulse.io.
Built with ❤️ for the Supabase community.
Share this article
Found this useful? Spread the word so more Supabase teams can optimize their observability stack.