Supabase
Watch auth requests, REST calls, realtime traffic, storage usage, and error counts for any Supabase project directly from your iPhone home screen.
Project health in five metrics
The Project module surfaces five 24-hour counters for any Supabase project you select: auth requests, realtime requests, REST API requests, storage requests, and total errors. Each metric includes a sparkline chart, so a traffic spike or a climbing error rate is visible at a glance without opening a browser tab. If errors are rising, you have a signal before users start reporting problems.
Your data, expressed as SQL
The SQL Query module accepts a read-only SELECT statement and turns the first row of results into a named widget. Up to ten columns become individual metric tiles on your home screen. Any aggregate you can write in SQL works here: active subscribers, rows inserted today, pending background jobs, unpaid invoices, conversion counts. No new tables or schema changes are required, just a query against data you already store in Supabase.
On-demand fetching with 30-day retention
PulseKit fetches Supabase data when you view a widget rather than polling on a fixed schedule, which keeps your project API quota low. Each result is retained for 30 days, giving you a rolling baseline to compare against. You can add separate widgets for multiple projects, making it straightforward to keep staging and production metrics visible side by side on the same home screen.
How to get your Supabase API key
Find your Personal Access Token in Supabase account settings at supabase.com/dashboard/account/tokens. The key starts with sbp_. Copy it now, since it will not be shown again.
Security
How we protect your credentials
Your Supabase API key is sealed on this device with AES-256-GCM before it ever leaves your iPhone. Only your device holds the unwrap secret, stored in the iOS Keychain. The PulseKit backend wraps that already-encrypted payload again with its STORAGE_SECRET and writes the double-envelope blob to Postgres, so the server never sees your plaintext key at rest. Each fetch request includes a one-time unwrap secret that decrypts the inner envelope only long enough to call Supabase. The key is scoped to this device, can be revoked from PulseKit at any time, and is never written to logs.
What you can track
Pick the metrics you care about and pin them as widgets.
Project
Track your Supabase project usage and errors
- 21Auth Requests (24h)
- 36Realtime Requests (24h)
- 17REST Requests (24h)
- 26Storage Requests (24h)
- 94Errors (24h)
SQL Query
Run a custom read-only SQL query and pin the first row as metrics
Numbers shown are illustrative — your widgets show your live data.
Who uses this
- Indie founders
You shipped your app on Supabase and want to know if it is gaining traction without logging in every morning. Pin auth requests and REST traffic to your home screen and check whether signups and API calls are growing, flat, or dropping, before you sit down at your desk.
- Backend developers
Error counts spiking after a deploy is the worst thing to find out from a user. The Errors (24h) metric with its chart gives you a persistent signal on your lock screen so an uptick is visible the moment you pick up your phone, not after a support ticket lands.
- SaaS builders
Standard project metrics only go so far. Use the SQL Query module to surface the numbers that matter to your business, active paid seats, trial conversions, jobs in a processing queue, and give each query its own named widget without writing any additional infrastructure.
- Full-stack teams
Running staging and production on separate Supabase projects means monitoring both. Add two Project widgets to your home screen and compare realtime and storage traffic across environments without switching tabs or dashboards.
FAQs
What Supabase metrics does PulseKit show?
PulseKit shows five 24-hour totals for each connected project: auth requests, realtime requests, REST API requests, storage requests, and total errors. Every metric includes a trend chart. You can also add custom metrics by writing a SQL query and pinning the first row of results as a widget, with up to ten columns mapped to individual tiles.
How do I connect my Supabase project to PulseKit?
You need a Personal Access Token from your Supabase account settings at supabase.com/dashboard/account/tokens. The token starts with sbp_. Copy it during creation because Supabase will not show it again. Paste it into PulseKit during setup, then select the project you want to track from the list PulseKit fetches automatically.
Can I run custom SQL queries as a home screen widget?
Yes. The SQL Query module accepts any read-only SELECT statement. PulseKit runs the query against your chosen project, takes the first row, and maps each column to a named metric tile. You can create multiple SQL Query widgets with different names and queries, one per business metric you want to track.
Can I monitor more than one Supabase project?
Yes. Add separate Project or SQL Query widgets for each Supabase project you want to watch. Each widget is configured independently, so you can keep a staging project and a production project on the same home screen with distinct labels.
How is my Supabase API key protected?
Your key is encrypted on-device with AES-256-GCM before it leaves your iPhone, using a secret stored in the iOS Keychain. The PulseKit backend wraps that already-encrypted payload again with its own storage secret, so the server never holds your plaintext key at rest. The key is scoped to your device and can be revoked from PulseKit at any time.
How often does PulseKit refresh Supabase data?
PulseKit fetches data on demand when you view a widget rather than polling continuously. This keeps calls to the Supabase API low and avoids consuming your project quota in the background. Data is cached for up to 30 days so you always have a historical baseline available for comparison.
Does the SQL Query module support write operations?
No. The SQL Query module is read-only. Only SELECT statements are accepted. This is intentional: PulseKit is a monitoring surface, not a database client, and restricting queries to reads ensures the integration cannot modify your data.
Add Supabase widgets to your iPhone
Install PulseKit, paste your credentials, pick a widget.