Skip to content
Merulan

Supabase setup

What an operator supplies to connect the Supabase Source, and the verification the provider requires.

Connecting Supabase accepts a named secret bundle the operator fills in. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Supabase refuses the connection until every item holds.

  • A Supabase project, and an administrator who may create a database role.
  • A database role narrowed to the tables a Pipeline reads, because the connection opens with exactly that role.
  • Network access from Merulan to the database host.

Credentials

Supabase stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • A host name, a port, a database name, a user, and a password, supplied together as one database bundle.

Scopes

Supabase carries no scope list in Merulan: the database role the administrator bound holds the requested scopes for this Source.

Supabase carries no consent screen here. Reach is the grant set on the role, so narrow the role rather than a scope list.

Verification

Workspace-issued credential governs the Supabase connection. The customer creates the role inside their own project, so the role grants are the whole verification story.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.