31 action definitionsBackend-as-a-Service

Supabase Connector

Catalogue summary: Backend platform management from support tickets.

Intended scope: Manage projects, edge functions, storage, secrets, auth configuration, database settings, and backups. Keva can check project health, manage secrets, review configurations, and handle edge functions through the Supabase Management API.

Unavailable for the WordPress-only design-partner release

Catalogue notice: platform-action execution is currently suspended. Definitions and illustrative workflows on this page do not prove self-serve setup, provider execution, rollback, or live verification.

31
Total Actions
2
Categories
21
Low Risk
5
Medium Risk
4
High Risk
5
Declared rollback support

Catalogued capabilities

Project managementEdge functionsStorage managementSecret managementAuth configDatabase configBackupsSSL enforcement

Source inventory only

Definitions and capability names are retained for catalogue reference. No workflow, action outcome, setup, or execution path is available for this release.

Related connectors

Other platforms in the Backend-as-a-Service category.

Cloudflare

62 definitions

Catalogue summary: DNS, CDN, security, and edge computing from support tickets.

AWS

40 definitions

Catalogue summary: Cloud infrastructure management from support tickets.

Vercel

29 definitions

Catalogue summary: Frontend hosting and deployment management from support tickets.

Railway

25 definitions

Catalogue summary: Cloud hosting and service management from support tickets.

Docker

30 definitions

Catalogue summary: Container lifecycle and infrastructure management from support tickets.

Kubernetes

30 definitions

Catalogue summary: Cluster management and workload orchestration from support tickets.

Evaluating Supabase support?

Review the 31 catalogue definitions and the proof still required for your environment.

No catalogue entry is presented as live behavioral proof.

Back to Connector Catalogue