> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Supabase on Vortex IQ
> Monitor Supabase health, cost and reliability signals, and catch incidents and runaway spend early.
Monitor Supabase health, cost and reliability signals, and catch incidents and runaway spend early.
[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=supabase)
performance signals
automated checks
prepared fixes
proven workflows
API operations
### What you can achieve
Capabilities are grouped around merchant outcomes, not API terminology.
Keep tracking, access and change under governed control.
Monitor orders, fulfilment, delivery and settlement.
Find failures, leaks and risks before they cost sales.
Find storefront, speed, accessibility and journey problems.
### From connection to verified outcome
The controlled sequence every capability follows. Nothing changes a connected system without the approval step.
Authorise the source. Scopes are shown before access is granted.
Watch the signals against your own baselines, not universal defaults.
Run checks and gather evidence specific to your store.
Explain what happened, why it matters and the proposed action.
You review scope, risk and reversibility before anything changes.
Apply through governed connector operations.
Confirm the intended result and keep the receipt.
No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
### Monitor performance
33 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
| Signal | Alert behaviour | What it tracks |
| ----------------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------- |
| **Active Realtime Channels** | Watch only | Description pending editorial review; the signal is live. |
| **Auth Active Users (24h)** | Watch only | Supabase Auth , users with a session in the last 24h. |
| **Auth Sign-In Error Rate %** | Merchant rule | Supabase-distinctive , Auth flow failures lock users out of the storefront. |
| **Database Query Error Rate %** | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
| **Database Query Error Rate Spike (>1% in 5m)** | Alert band 0.1 / 1 | Alerts for Database Query Error Rate Spike (>1% in 5m). |
| **Edge Function Error Rate %** | Merchant rule | Supabase Edge Functions (Deno) invocation failures. |
| **PostgREST 5xx Error Rate %** | Alert band 0.1 / 1 | Description pending editorial review; the signal is live. |
| **PostgREST 5xx Error Spike (>1% in 5m)** | Alert band 0.1 / 1 | Supabase-distinctive , PostgREST is the merchant app's actual API. 5xx = app down. |
| **PostgREST API Latency p95 (ms)** | Alert band 50 / 200 | Supabase-distinctive , the auto-generated REST layer is what the merchant's app actually calls. |
| **PostgREST API Latency p99 (ms)** | Alert band 100 / 500 | Description pending editorial review; the signal is live. |
| **PostgREST Request Rate (req/sec)** | Watch only | PostgREST Request Rate (req/sec) over time. |
| **Realtime Connected Clients** | Watch only | Supabase-distinctive , WebSocket subscribers on Realtime channels. |
| **Realtime Disconnect Rate (per min)** | Merchant rule | Disconnect storms = Realtime instability; clients lose live updates. |
| Signal | Alert behaviour | What it tracks |
| -------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------ |
| **Buffer Cache Hit Rate %** | Alert band 95 / 80 | Description pending editorial review; the signal is live. |
| **Connections In Use** | Watch only | Description pending editorial review; the signal is live. |
| **Database Disk Usage %** | Alert band 70 / 90 | Supabase tiers cap disk , hitting the cap puts the project in read-only / restricted mode. |
| **Database Queries per Second (live)** | Watch only | Description pending editorial review; the signal is live. |
| **Last Backup Age (hours)** | Alert band 24 / 72 | Supabase daily backups (Pro+); Point-in-Time Recovery on higher tiers. Free tier has no backup. |
| **Memory Usage %** | Merchant rule | Description pending editorial review; the signal is live. |
| **Project Uptime** | Watch only | Description pending editorial review; the signal is live. |
| **Read Replica Lag (seconds)** | Alert band 1 / 10 | Supabase read replicas are a paid feature , regional. Lag affects read-routed queries. |
| **Read Replicas** | Watch only | Description pending editorial review; the signal is live. |
| **Supabase Health Score** | Merchant rule | Description pending editorial review; the signal is live. |
| **Supavisor Pool Saturation %** | Alert band 70 / 90 | Supavisor (Supabase's connection pooler) saturation. Free / Pro tiers have hard connection caps. |
| **Supavisor Pool at >90% Saturation** | Alert band 70 / 90 | Alerts for Supavisor Pool at >90% Saturation. |
| Signal | Alert behaviour | What it tracks |
| ------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------- |
| **Slow PostgREST Queries During Checkout Window** | Merchant rule | Slow PostgREST Queries During Checkout Window, broken down by row. |
| **Supabase Products Table vs Ecom Catalog** | Merchant rule | Description pending editorial review; the signal is live. |
| **Supabase QPS Spike vs Ecom Order Rate** | Merchant rule | Description pending editorial review; the signal is live. |
| **Supavisor Pool Saturation vs Traffic Burst** | Alert band 70 / 90 | Supabase-distinctive , Supavisor pool caps are tier-bound; burst on free / pro tier exhausts fast. |
| Signal | Alert behaviour | What it tracks |
| ----------------------------------- | ---------------- | --------------------------------------------------------- |
| **Deadlocks (last 5m)** | Alert band 0 / 5 | Description pending editorial review; the signal is live. |
| **Postgres Query Latency p95 (ms)** | Watch only | Description pending editorial review; the signal is live. |
| **Slow-Query Rate %** | Alert band 1 / 5 | Description pending editorial review; the signal is live. |
| **Top 10 Slowest Queries** | Watch only | Top 10 Slowest Queries, broken down by row. |
### Audit risks and opportunities
A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.
**Severity** critical · **Outcome** Customer experience · **Fix status** Report only
At 90% of the connection pool in use, the database is close to refusing new connections outright. Once it does, every part of the application that needs a fresh database connection, including new customer sessions and checkout, starts failing, not just slowing down.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-CAP-001`
**Severity** critical · **Outcome** Run operations · **Fix status** Report only
A database that runs out of disk stops accepting writes entirely, which for most stores means orders, inventory updates and customer records stop being saved, not just that the database gets slower. There is very little runway left at 90%.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-CAP-002`
**Severity** critical · **Outcome** Run operations · **Fix status** Report only
More than 1 in 100 queries is failing right now. Depending on what those queries do, this can mean orders not saving, pages failing to load product or customer data, or background jobs silently dropping work, and a rate this high in a 5-minute window is an active incident, not background noise.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-ERR-001`
**Severity** high · **Outcome** Run operations · **Fix status** Report only
If something goes wrong with this database right now, the most recent point it can be restored to is over 3 days old. Every order, customer record and inventory change since that backup would be unrecoverable in a real incident, not just delayed.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-BAK-001`
**Severity** high · **Outcome** Run operations · **Fix status** Report only
Anything reading from the replica, reports, dashboards, or read traffic split off the primary for capacity, is now up to 10+ seconds stale. If the primary fails while lag is this high, the replica is also that far behind on failover, which is a bigger problem than the staleness alone.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-REP-001`
**Severity** high · **Outcome** Customer experience · **Fix status** Report only
More than 1 in 20 queries is landing in the slow bucket. That is frequent enough to be a pattern, not noise, and it means a meaningful share of every page load or job that touches this database is paying the slow-query cost, not just an unlucky occasional request.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-PERF-002`
**Severity** high · **Outcome** Customer experience · **Fix status** Report only
One in twenty queries against this database is taking over 200ms, sustained for at least 15 minutes, not a brief spike. Any storefront page, checkout step or order sync that depends on this database inherits that slowness directly, and a sustained p95 this high is usually already visible to customer
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-PERF-001`
**Severity** medium · **Outcome** Run operations · **Fix status** Report only
More than 1 in 5 reads is missing the cache and going to disk instead, which is markedly slower. This shows up as everything the database does feeling incrementally heavier, rather than as one obvious failure.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-CACHE-001`
**Severity** medium · **Outcome** Protect revenue · **Fix status** Report only
A deadlock means two operations blocked each other and the database had to kill one of them; whatever that transaction was doing (placing an order, updating stock, writing a record) failed and, depending on how the application handles it, may not have been retried.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `DB-PERF-003`
#### Build your own automated fixes
Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
### Automate approved work
Vortex IQ is integrated with **6 read** and **0 write** operations across pgstatactivitys, pgstatreplications, projects, projectanalyticsendpointlogalls, realtimetenanthealths, rpcpgstatstatements on Supabase. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.
Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.
[Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=supabase)
#### Ready to build your first Supabase workflow
Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.
| Resource | Read operations | Write operations |
| ------------------------------- | --------------- | ---------------- |
| pgstatactivitys | 1 | 0 |
| pgstatreplications | 1 | 0 |
| projects | 1 | 0 |
| projectanalyticsendpointlogalls | 1 | 0 |
| realtimetenanthealths | 1 | 0 |
| rpcpgstatstatements | 1 | 0 |
Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.