How to Connect Your Neon PostgreSQL Database to Indiequery

Last updated: November 21, 2025

Connect your Neon 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 Neon and connect in minutes.

Get Your Neon Connection Details

Log into the Neon console at console.neon.tech and select your project. Click the Connect button at the top of the dashboard to open the connection details modal.

The modal shows your connection information with selectable options:

  • Branch - Choose your branch (default is main)
  • Database - Your database name (default is neondb)
  • Role - Your database role (default is neondb_owner)
  • Compute - Your compute endpoint Toggle off Connection pooling at the bottom of the modal. Neon defaults to pooled connections, but Indiequery works best with direct connections for standard PostgreSQL protocol compatibility.

With pooling disabled, you'll see a connection string like:

postgresql://neondb_owner:[password]@ep-cool-darkness-123456.us-east-2.aws.neon.tech/neondb?sslmode=require

From this string, extract:

  • Host - The part after @ and before / (ending in .aws.neon.tech)
  • Port - 5432 (standard PostgreSQL port)
  • Database - The part after the host and / (usually neondb)
  • Username - The part before : (usually neondb_owner)
  • Password - Your role password If you don't see your password in the connection string, click Reset password to generate a new one. Copy it immediately - Neon only shows it once.

Connect to Indiequery

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

  1. Host - Your compute endpoint hostname (ending in .aws.neon.tech)
  2. Port - Enter 5432
  3. Database - Your database name (default is neondb)
  4. Username - Your role name (default is neondb_owner)
  5. Password - Your role password
  6. Keep "Require SSL" checked (Neon requires SSL)
  7. Name your connection (e.g., "Neon Production")
  8. Click Add Connection Indiequery tests the connection automatically. Once successful, you're ready to query your Neon database.

Configure IP Allow (Optional)

Neon accepts connections from any IP address by default. For additional security, you can restrict access to specific IP addresses.

Navigate to your project Settings > Network security > IP Allow. Click Add and enter Indiequery's IP address: 91.98.141.61

You can specify individual IPs, ranges, or CIDR notation. Separate multiple entries with commas. Once configured, only whitelisted IP addresses can connect to your database.

IP Allow applies to all branches by default, or you can restrict it to protected branches only.

Connection Pooling vs Direct Connection

Neon offers two connection modes:

Connection pooling - Uses PgBouncer to handle many concurrent connections efficiently. The hostname includes -pooler in the endpoint (e.g., ep-cool-darkness-123456-pooler.us-east-2.aws.neon.tech). Best for serverless applications with many short-lived connections.

Direct connection - Standard PostgreSQL connection to port 5432. The hostname doesn't include -pooler. Best for traditional applications and tools like Indiequery that maintain persistent connections.

Always use direct connection for Indiequery. Toggle off "Connection pooling" in the Neon console when copying connection details.

SSL/TLS Requirement

Neon requires SSL/TLS for all connections. Keep the "Require SSL" checkbox checked when connecting in Indiequery.

Neon supports TLS 1.2 and higher. Older TLS versions (1.0 and 1.1) are rejected. Indiequery handles SSL automatically when the checkbox is enabled.

Common Connection Issues

"Connection timed out" or "Connection refused"

Verify you're using the direct connection hostname (without -pooler). Check that you toggled off "Connection pooling" in the Neon console. If you enabled IP Allow, confirm 91.98.141.61 is in your allowlist. Ensure your Neon project status shows Active.

"SSL connection required"

Keep "Require SSL" checked in Indiequery. Neon requires encrypted connections and rejects unencrypted attempts.

"Authentication failed"

Double-check your role password. If you don't remember it, click Reset password in the Neon console for your role. Copy the new password immediately - Neon only displays it once.

Verify your username matches the role name (default is neondb_owner, not just neondb).

"Database does not exist"

Check the Databases section in Neon to see available databases. The default database is neondb, but you may have created custom databases. Database names are case-sensitive.

"Too many connections"

If you're hitting connection limits, you may need to use connection pooling or upgrade your Neon plan. However, this shouldn't happen with Indiequery since it maintains a small number of persistent connections.

Connect to Read Replicas

Neon supports read replicas for offloading analytics and reporting queries. Connect Indiequery to a read replica instead of your primary compute for safer querying without impacting production performance.

In the Neon console, navigate to your branch and click Add Read Replica. Choose your replica configuration and wait for it to become active.

Once the read replica is running, click Connect and select the read replica from the Compute dropdown. Toggle off connection pooling and copy the connection details.

Use the read replica's connection details in Indiequery. Queries run against the replica access the same data but don't affect your primary compute's resources.

Read replicas are available on all Neon plans, including the Free plan (limited to 3 read replicas per project).

Branches and Environments

Neon uses branches to create isolated copies of your database for development and testing. Each branch gets its own compute and connection details.

To connect Indiequery to a non-production branch, click Connect in the Neon console and select the branch from the dropdown. Copy the branch's connection details (remember to toggle off pooling) and create a separate connection in Indiequery.

This lets you test queries on development branches without affecting production data.

Serverless Architecture Benefits

Neon's serverless architecture means your compute automatically scales to zero when inactive. This doesn't affect Indiequery connections - when you query your database, Neon wakes the compute instantly (typically under 500ms).

You only pay for active compute time, making Neon cost-effective for databases that aren't queried constantly. Indiequery works seamlessly with Neon's auto-suspend and auto-resume behavior.

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 Neon database.
← Back to Hosting Integration