Sanaf AI
Start free
Developer Tools

Supabase, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Supabase account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 79 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Supabase is

Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications

You sign in with your own Supabase account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Supabase.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Supabase. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Supabase account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

79 tools it already has

What it can do in Supabase

These are the ready-made tools your AI employee already has in Supabase. It is not limited to them, but it never has to be taught these.

  • Activate vanity subdomain for projectActivates a vanity subdomain for the specified supabase project, requiring subsequent dns configuration for the subdomain to become operational.
  • Authorize user through OAuthGenerates a supabase oauth 2.0 authorization url for user redirection, requiring a pre-registered client id and a redirect uri that matches one of its pre-registered uris.
  • Beta activate custom hostname for projectActivates a previously configured custom hostname for a supabase project, assuming dns settings are verified externally.
  • Beta get project's custom hostname configRetrieves a supabase project's custom hostname configuration, including its status, ssl certificate, and ownership verification, noting that availability may depend on the project'
  • Beta remove a read replicaIrreversibly initiates the removal of a specified read replica from an existing supabase project, confirming only the start of the process, not its completion.
  • Beta update project network restrictionsUpdates and applies network access restrictions (ipv4/ipv6 cidr lists) for a supabase project, which may terminate existing connections not matching the new rules.
  • Check vanity subdomain availabilityChecks if a specific vanity subdomain is available for a supabase project; this action does not reserve or assign the subdomain.
  • Create a database branchCreates a new, isolated database branch from an existing supabase project (identified by ref), useful for setting up separate environments like development or testing, which can op
  • Create a functionCreates a new serverless edge function for a supabase project (identified by ref), requiring valid javascript/typescript in body and a project-unique slug 1 identifier.
  • Create a new third-party auth integrationCall this to add a new third-party authentication method (oidc or jwks) to a supabase project for integrating external identity providers (e.g., for sso); the api may also support
  • Create an organizationCreates a new supabase organization, which serves as a top-level container for projects, billing, and team access.
  • Create new projectCreates a new supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
  • Create project api keyCreates a 'publishable' or 'secret' api key for an existing supabase project, optionally with a description; 'secret' keys can have customized jwt templates.
  • Create SSO provider configurationCreates a new saml 2.0 single sign-on (sso) provider for a supabase project, requiring either metadata xml or metadata url for saml idp configuration.
  • Delete an API key from the projectPermanently deletes a specific api key (identified by id) from a supabase project (identified by ref), revoking its access.
  • Delete an edge function by slugPermanently deletes a specific edge function (by function slug) from a supabase project (by ref); this action is irreversible and requires prior existence of both project and funct
  • Delete branch by idPermanently and irreversibly deletes a specific, non-default database branch by its branch id, without affecting other branches.
  • Delete custom hostname configDeletes an active custom hostname configuration for the project identified by ref, reverting to the default supabase-provided hostname; this action immediately makes the project in
  • Delete project by refPermanently and irreversibly deletes a supabase project, identified by its unique ref id, resulting in complete data loss.
  • Delete third party auth configRemoves a third-party authentication provider (e.g., google, github) from a supabase project's configuration; this immediately prevents users from logging in via that method.
  • Delete vanity subdomain for projectPermanently and irreversibly deletes an active vanity subdomain configuration for the specified supabase project, reverting it to its default supabase url.
  • Deploy functionDeploys edge functions to a supabase project using multipart upload.
  • Disable preview branchingDisables the preview branching feature for an existing supabase project, identified by its unique reference id (ref).
  • Disable project readonly modeTemporarily disables a supabase project's read-only mode for 15 minutes to allow write operations (e.g., for maintenance or critical updates), after which it automatically reverts
  • Enable project database webhooksEnables database webhooks for the supabase project ref, triggering real-time notifications for insert, update, or delete events.
  • Exchange auth code for access and refresh token(beta) implements the oauth 2.0 token endpoint to exchange an authorization code or refresh token for access/refresh tokens, based on grant type.
  • Execute project database queryExecutes a given sql query against the project's database; use for advanced data operations or when standard api endpoints are insufficient, ensuring queries are valid postgresql a
  • Generate TypeScript typesGenerates and retrieves typescript types from a supabase project's database; any schemas specified in included schemas must exist in the project.
  • Get a specific SQL snippetRetrieves a specific sql snippet by its unique identifier.
  • Get a SSO provider by its UUIDRetrieves the configuration details for a specific single sign-on (sso) provider (e.g., saml, google, github, azure ad), identified by its uuid, within a supabase project.
  • Get a third-party integrationRetrieves the detailed configuration for a specific third-party authentication (tpa) provider, identified by tpa id, within an existing supabase project specified by ref.
  • Get current vanity subdomain configFetches the current vanity subdomain configuration, including its status and custom domain name, for a supabase project identified by its reference id.
  • Get database branch configRetrieves the read-only configuration and status for a supabase database branch, typically for monitoring or verifying its settings.
  • Get information about an organizationFetches comprehensive details for a specific supabase organization using its unique slug.
  • Get project API keysRetrieves all api keys for an existing supabase project, specified by its unique reference id (ref); this is a read-only operation.
  • Get project PgBouncer configRetrieves the active pgbouncer configuration (postgresql connection pooler) for a supabase project, used for performance tuning, auditing, or getting the connection string.
  • Get project pgsodium configRetrieves the pgsodium configuration, including the root encryption key, for an existing supabase project identified by its ref.
  • Get project postgres configRetrieves the current read-only postgresql database configuration for a specified supabase project's ref, noting that some advanced or security-sensitive details might be omitted f
  • Get project SSL enforcement configurationRetrieves the ssl enforcement configuration for a specified supabase project, indicating if ssl connections are mandated for its database.
  • Get project Supavisor configurationRetrieves the supavisor (connection pooler) configuration for a specified supabase project, identified by its reference id.
  • Get Project Upgrade EligibilityChecks a supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade.
  • Get project upgrade statusRetrieves the latest status of a supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades.
  • Get project's auth configRetrieves the project's complete read-only authentication configuration, detailing all settings (e.g., providers, mfa, email/sms, jwt, security policies) but excluding sensitive se
  • Get project's PostgREST configRetrieves the postgrest configuration for a specific supabase project.
  • Get project's read-only mode statusRetrieves the read-only mode status for a specified supabase project to check its operational state; this action does not change the read-only state.
  • Get project's service health statusRetrieves the current health status for a supabase project, for specified services or all services if the 'services' list is omitted.
  • Get Table SchemasRetrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate sql queries.
  • List all bucketsRetrieves a list of all storage buckets for a supabase project, without returning bucket contents or access policies.
  • List all database branchesLists all database branches for a specified supabase project, used for isolated development and testing of schema changes; ensure the project reference id is valid.
  • List all functionsLists metadata for all edge functions in a supabase project (specified by 'ref'), excluding function code or logs; the project must exist.
  • List all organizationsLists all organizations (id and name only) associated with the supabase account, excluding project details within these organizations.
  • List all projectsRetrieves a list of all supabase projects, including their id, name, region, and status, for the authenticated user.
  • List all secretsRetrieves all secrets for a supabase project using its reference id; secret values in the response may be masked.
  • List all SSO providersLists all configured single sign-on (sso) providers for a supabase project, requiring the project reference id (ref) of an existing project.
  • List members of an organizationRetrieves all members of a supabase organization, identified by its unique slug, including their user id, username, email, role, and mfa status.
  • List project database backupsLists all database backups for a supabase project, providing details on existing backups but not creating new ones or performing restores; availability may depend on plan and confi
  • List SQL snippets for the logged in userRetrieves a list of sql snippets for the logged-in user, optionally filtered by a specific supabase project if project ref is provided.
  • List third-party auth integrations for projectLists all configured third-party authentication provider integrations for an existing supabase project (using its ref), suitable for read-only auditing or verifying current authent
  • Remove an SSO providerDeletes a specific sso provider by its id (provider id) from a supabase project (ref), which disables it and returns its details; ensure this action will not inadvertently lock out
  • Remove project network bansRemoves specified ipv4 addresses from a supabase project's network ban list, granting immediate access; ips not currently banned are ignored.
  • Reset a database branchResets an existing supabase database branch, identified by branch id, to its initial clean state, irreversibly deleting all its current data and schema changes.
  • Restore database PITR backupRestores a supabase project's database to a specific unix timestamp using point-in-time recovery (pitr), overwriting the current state; requires a paid plan with pitr and physical
  • Retrieve a functionRetrieves detailed information, metadata, configuration, and status for a specific edge function using its project reference id and function slug.
  • Retrieve a function bodyRetrieves the source code (body) for a specified serverless edge function using its project reference and function slug; this is a read-only operation that does not execute the fun
  • Retrieve network bans for projectRetrieves the list of banned ipv4 addresses for a supabase project using its unique project reference string; this is a read-only operation.
  • Retrieve project network restrictionsRetrieves the current network restriction settings (e.g., ip whitelists) for a supabase project using its reference id; this is a read-only operation for auditing or verifying netw
  • Reverify custom hostnameRe-verifies dns and ssl configurations for an existing custom hostname associated with a supabase project.
  • Setup read replica for projectProvisions a read-only replica for a supabase project in a specified, supabase-supported aws region to enhance read performance and reduce latency.
  • Update a functionUpdates an existing supabase edge function's properties (like name, slug, source code, jwt settings, import map) identified by project ref and function slug, supporting plain text
  • Update an API key for the projectUpdates an existing supabase project api key's description and/or secret jwt template (which defines its role); does not regenerate the key string.
  • Update an SSO provider by its UUIDUpdates an existing sso provider's saml metadata, associated email domains, or attribute mappings for a supabase project, identified by ref and provider id.
  • Update database branch configUpdates the configuration of a supabase database branch, allowing modification of its name, associated git branch, reset-on-push behavior, persistence, and status.
  • Update database pooler configUpdates the supavisor (database pooler) configuration, such as default pool size, for an existing supabase project identified by ref; the pool mode parameter in the request is depr
  • Update pgsodium root keyCritically updates or initializes a supabase project's pgsodium root encryption key for security setup or key rotation, requiring secure backup of the new key to prevent irreversib
  • Update project's custom hostname configurationUpdates the custom hostname for a supabase project, requiring subsequent dns changes to a user-controlled domain for ssl certificate issuance and domain ownership.
  • Update project's postgres configUpdates specified postgresql configuration parameters for an existing supabase project (ref) to optimize database performance; note that unspecified parameters remain unchanged, an
  • Update project's PostgREST configUpdates postgrest configuration settings (e.g., max rows, db pool, db schema, db extra search path) for a supabase project to fine-tune api performance, data exposure, and database
  • Update SSL enforcement configUpdates the ssl enforcement configuration (enable/disable) for a specified supabase project's database.
  • Upgrade the project's PostgreSQL versionInitiates an asynchronous upgrade of a supabase project's postgresql database to a specified target version from a selected release channel, returning a tracking id to monitor stat
Access, and who is in charge of it

You stay the boss of your Supabase account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Supabase account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Supabase is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Supabase and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Supabase

Can an AI employee really work inside Supabase?
Yes. It signs in to your own Supabase account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Supabase?
No. Nothing moves and nothing is replaced. Your records stay in Supabase, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Supabase account?
You sign in with your own Supabase account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Supabase?
It has 79 ready-made tools in Supabase today, among them Activate vanity subdomain for project, Authorize user through OAuth and Beta activate custom hostname for project. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Supabase and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Supabase and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Supabase?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Supabase is written down with what it did and when.