Skip to content
Now accepting Q2 projects — limited slots available. Get started →

We run socialanimal.dev on Supabase.
Here's how it's doing right now.

Updated every 5 minutes from our real Prometheus endpoint. Zero mock data. If our database hiccups, you see it here before anyone tells us.

socialanimal.dev — live Supabase metrics
Captured 108h ago · scrapes every 5 min · we run this site on Supabase
4 / 100
CPU
4% utilisation
52 / 100
RAM
472.1 MB / 0.9 GB
73 / 100
Disk
7.0 GB / 9.6 GB
100 / 100
Network out
69620098 KB/s upstream

Last 24 hours

Trend lines for every 5-minute scrape window.

Trend charts populate once the scraper has collected a few snapshots. First scrape runs every 5 minutes.

How this works

01

Scrape Supabase's Prometheus endpoint

Vercel cron pings customer/v1/privileged/metrics on our project every 5 minutes. Returns standard Prometheus text format with ~200 metrics.

02

Parse + project

Our scraper extracts CPU / RAM / disk / network from the node_exporter feed + connection counts + cache hit ratio from postgres_exporter.

03

Persist to Supabase itself

One row per scrape in metrics_snapshots. ~288 rows/day. The whole pipeline runs on the same database we're measuring.

04

Render with ISR

This page re-renders every 60 seconds. Charts pull from a public view filtered to safe-to-share metrics (no query payloads, no user counts).

Want this for your Supabase stack?

Two-week sprint: production-ready setup, Prometheus scrape, RLS audit, alerting, dashboards. Fixed $8k.

Book a Supabase consult →
Get in touch

Let's build
something together.

Whether it's a migration, a new build, or an SEO challenge — the Social Animal team would love to hear from you.

Get in touch →