Skip to main content

​
Prerequisites

​
Understanding Supabase connection modes

Supabase offers two ways to connect to your database. Choosing the right one matters:
For VexiData, we recommend the Transaction Pooler (port 6543). VexiData connects on-demand when running queries, so the pooler is the best fit and provides better performance.

​
Connect Supabase to VexiData

1

Get your Supabase connection details

  1. Log in to your Supabase Dashboard
  2. Select the project you want to connect
  3. Go to Project Settings (gear icon) > Database
  4. Under Connection string, select the URI tab
  5. Choose Transaction Pooler mode (recommended)
  6. Copy the connection string — it looks like this:
Extract the following values from the connection string:
2

Whitelist VexiData's IP addresses

If your Supabase project has network restrictions enabled, add VexiData’s IP addresses to your allowlist:
  • 46.101.71.122
You can manage network restrictions in Project Settings > Database > Network Restrictions in Supabase.
By default, Supabase allows connections from all IP addresses. You only need this step if you have explicitly enabled network restrictions.
3

Add the connection in VexiData

  1. Go to Data Sources in VexiData
  2. Click PostgreSQL to open the connection form
  3. Fill in the details:
4

Test and save

Click Test & Save Connection. VexiData will verify it can reach your database. Once connected, your schema will be analyzed automatically.

​
Finding your database password

If you don’t remember your database password, you can reset it in Supabase:
  1. Go to Project Settings > Database
  2. Under Database Password, click Reset Database Password
Resetting your database password will break any existing connections using the old password. Update them after resetting.

​
Troubleshooting

  • Verify that VexiData’s IP addresses are allowlisted if you have network restrictions enabled
  • Check that you’re using the correct host and port for your chosen connection mode
  • Ensure your Supabase project is not paused — free-tier projects pause after inactivity
  • Double-check your username format — the Transaction Pooler requires postgres.[project-ref], not just postgres
  • Verify your password is correct. If unsure, reset it in Supabase Project Settings
  • Make sure you’re not mixing up Direct Connection and Transaction Pooler credentials
  • Confirm your tables are in the public schema. If they’re in a custom schema, update the Schema field in VexiData
  • Check that the database user has SELECT permissions on the tables you want to query
  • If your Supabase project is on the free tier, it may be running on shared infrastructure with limited resources
  • Consider upgrading your Supabase plan for better performance