How to Connect Your Supabase PostgreSQL Database to Indiequery

Last updated: November 21, 2025

Connect your Supabase PostgreSQL database to Indiequery to query and explore data through a web interface. No desktop apps, no command line. Just grab your connection details from Supabase and connect in minutes.

Get Your Supabase Connection Details

Log into your Supabase dashboard at app.supabase.com and select your project. Click the Connect button at the top of your project page to view connection information.

You'll see connection strings for different modes. For Indiequery, use Session mode - it works with both IPv4 and IPv6 and supports the full range of PostgreSQL features.

The connection string format shows:

postgres://postgres.[PROJECT-ID]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:5432/postgres

From this string, you'll need:

  • Host - The part after @ and before the port (ending in .pooler.supabase.com)
  • Port - 5432
  • Database - postgres (the part after the port and /)
  • Username - postgres.[PROJECT-ID] (the part before the password)
  • Password - Your database password If you don't see your password in the connection string, go to Settings (gear icon) > Database in the sidebar. Scroll to Database password and click Reset database password to generate a new one. Copy it immediately - Supabase only shows it once.

Connect to Indiequery

Navigate to app.indiequery.com and click Add Database Connection. Enter your connection details from Supabase:

  1. Host - The pooler hostname from the connection string (ending in .pooler.supabase.com)
  2. Port - Enter 5432
  3. Database - Enter postgres
  4. Username - Enter your full username including project ID (format: postgres.[PROJECT-ID])
  5. Password - Your database password
  6. Keep "Require SSL" checked (Supabase requires SSL)
  7. Name your connection (e.g., "Supabase Production")
  8. Click Add Connection Indiequery tests the connection automatically. Once successful, you're ready to query your Supabase database.

Connection Modes Explained

Supabase offers three connection modes:

Session mode (recommended for Indiequery) - Uses Supavisor pooler on port 5432. Supports both IPv4 and IPv6. Works with prepared statements and all PostgreSQL features. Best for persistent connections like Indiequery.

Transaction mode - Uses Supavisor pooler on port 6543. Designed for serverless and edge functions with temporary connections. Doesn't support prepared statements, so some database tools may not work properly.

Direct connection - Port 5432 without pooling. Uses IPv6 only unless you purchase the IPv4 addon ($4/month). Limited to 60 concurrent connections on free tier. Only use if you need features that don't work through the pooler.

Always use Session mode (port 5432 with the pooler hostname) for Indiequery. It provides the best compatibility and performance.

SSL/TLS Requirement

Supabase requires SSL/TLS for all database connections. Keep the "Require SSL" checkbox checked when connecting in Indiequery. Connections without SSL will fail.

You can download the server root certificate from your Supabase dashboard (available via the Connect button), but Indiequery handles SSL verification automatically.

Network Restrictions

Supabase's free tier allows connections from any IP address. Pro and Enterprise plans can restrict database access to specific IP addresses for additional security.

If you've enabled network restrictions in Settings > Database, add Indiequery's IP address to the allowed list: 91.98.141.61/32

Without whitelisting this IP, Indiequery won't connect even with valid credentials.

Common Connection Issues

"Connection timed out" or "Connection refused"

Verify you're using the Session mode connection string with the pooler hostname (ending in .pooler.supabase.com) and port 5432. Don't use the direct connection details. Check your Supabase project status shows Active. If you enabled network restrictions, confirm Indiequery's IP (91.98.141.61) is whitelisted.

"SSL connection required"

Keep "Require SSL" checked in Indiequery. Supabase requires encrypted connections for all database access.

"Authentication failed"

Double-check your database password. If you don't remember it, go to Settings > Database in Supabase and click Reset database password. Copy the new password immediately - Supabase only shows it once.

Verify your username includes the full postgres.[PROJECT-ID] format from the connection string, not just postgres.

"Database does not exist"

The default database name is postgres. If you created custom databases in your Supabase project, use that name instead. Database names are case-sensitive.

Special characters in password

If your password contains special characters (like =, @, or /), make sure to copy it exactly as shown. Supabase connection strings percent-encode special characters, but when entering individual connection parameters in Indiequery, use the actual password without percent-encoding.

Read Replicas

Supabase Pro and Teams plans support read replicas in different geographic regions. Connect Indiequery to a read replica for safer querying and better performance if you're located far from your primary database region.

In your Supabase dashboard, go to Settings > Infrastructure > Read Replicas. Click Deploy a read replica and choose your region. Once the replica is active, it gets its own connection details with a different host.

Use the replica's Session mode connection details in Indiequery for read-only queries that don't affect your primary database performance.

Next Steps

Once connected:

  • Browse tables and schemas in the schema explorer
  • Run SQL queries with autocomplete
  • Create charts and visualizations
  • Save queries for reuse
  • Build dashboards
  • Export results to CSV, JSON, or Markdown Navigate to the query editor and start exploring your Supabase data.
← Back to Hosting Integration