Supabase Integration

What OpsCompanion Monitors in Supabase

Projects

• Project listing and status
• Project health checks
• API key management (names only, not values)
• Project settings and configuration

Database

• Table listings across all schemas
• Column definitions and data types
• Read-only SQL queries (SELECT and EXPLAIN only)
• Installed Postgres extensions
• Index and constraint information

Authentication

• User listings with activity timestamps
• Auth provider configuration (Google, GitHub, Apple, etc.)
• User statistics (total, active, new signups)
• MFA and captcha settings
• Auth email/phone configuration

Storage

• Bucket listings with access policies
• Object browsing within buckets
• Storage usage statistics per bucket
• File size limit and MIME type configurations

Edge Functions

• Deployed function listings
• Function details (version, status, JWT verification)
• Function metadata and configuration

How Supabase Integration Works

1. You authorize OpsCompanion via Supabase OAuth
2. OpsCompanion receives a scoped access token
3. The Management API is used for project-level operations
4. Database queries run through the Management API (read-only)
5. Tokens are refreshed automatically

What OpsCompanion Can Access

• Project metadata and configuration
• Database schema and read-only queries
• Auth user listings and configuration
• Storage bucket and object metadata
• Edge Function listings and details

What OpsCompanion Cannot Access

• Database passwords or connection strings
• Secret values or API keys (only names)
• Write operations (no INSERT, UPDATE, DELETE, DROP)
• Billing or payment information
• RLS policy bypass

Constraints

• Read-only access via Management API
• SQL queries are restricted to SELECT and EXPLAIN
• Query results are limited to 100 rows by default
• OAuth tokens are scoped to your authorized organizations
• Cannot create, update, or delete resources

Setup

Supabase Setup Guide - Authorize OpsCompanion via Supabase OAuth.