Supabase
Purpose
Collects Supabase organizations, projects, databases, API key metadata, edge functions, storage, authentication settings, network controls, branches, and security advisor findings.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into SubImage's managed vault. See Secrets for details.
Required Fields
| Field | Secret? | Description |
|---|---|---|
supabase_access_token |
Yes | Supabase personal access token |
Optional Fields
| Field | Description |
|---|---|
supabase_organizations |
Comma-separated organization slugs. All accessible organizations sync by default. |
supabase_base_url |
Management API URL. Defaults to https://api.supabase.com. |
Setup Steps
- Open the Supabase access tokens page.
- Create a personal access token from an account with read access to every organization you want to inventory.
- In SubImage, enter the token in
supabase_access_token. - To limit the sync, enter organization slugs separated by commas in
supabase_organizations. - Save the module and run a sync.
Notes
The integration only makes read requests. Secret values returned by some Management API endpoints are discarded before graph ingestion. Features unavailable on the current Supabase plan are skipped without deleting previously collected data.