DatabasesAvailable

Supabase

Postgres with auth, storage and realtime. Connect the database and the REST endpoint.

What it enables in Codexa

Use the Supabase Postgres database with the same schema browser and SQL runner as the PostgreSQL integration.
Keep the project URL and anon key alongside the database so generated apps can be configured consistently.

Fields on the workspace connection form. Password-type fields are encrypted before storage and never shown again.

Field	Type	Required	Example
Project URL `projectUrl`	url	Yes	https://xyzcompany.supabase.co
Anon (public) key `anonKey`	text	Yes	eyJhbGciOi...
Database connection string `connectionString`	secret	Yes	postgresql://postgres:[password]@db.xyz.supabase.co:5432/postgres

Open Settings → Integrations in your workspace (requires the admin or owner role).
Choose the provider, give the connection a name, and fill in the fields listed above. Secret fields are encrypted before they are stored and are never sent back to the browser.
Click Test connection. Codexa makes a single read-only request to the provider to confirm the credentials work.
Save. The connection is now available to projects in this workspace.

The database connection string from Supabase → Project settings → Database.
The anon (public) key. The service role key is not required and should not be pasted into Codexa.

Supabase Auth, Storage and Realtime are not integrated; only the Postgres database and the REST endpoint details are used.
Row Level Security policies are not managed by Codexa; manage them in the Supabase dashboard or with SQL.

Create a free account, add the connections your project needs, and let the AI agent build against them.