Skip to main content

​
Prerequisites

  • A Neon account with an existing project
  • A VexiData account

​
Understanding Neon connection modes

Neon offers two ways to connect — with or without connection pooling. The difference is in the hostname:
For VexiData, we recommend the Pooled Connection. VexiData connects on-demand when running queries, so the pooler (PgBouncer) provides better performance and handles connection limits more efficiently.

​
Connect Neon to VexiData

1

Get your Neon connection details

  1. Log in to your Neon Console
  2. Select the project you want to connect
  3. In the Dashboard, find the Connection Details widget
  4. Select the Branch and Database you want to connect (Neon projects can have multiple branches)
  5. Make sure Pooled connection is toggled on (recommended)
  6. Switch to the Parameters only view to see the individual values:
If you don’t see the password, click Show password or Reset password in the Connection Details widget. You can also find connection strings under Project Settings > Connection String.
2

Whitelist VexiData's IP addresses (if needed)

If your Neon project has IP Allow enabled (available on paid plans), add VexiData’s IP addresses to your trusted list:
  • 46.101.71.122
You can manage this in your Neon project under Settings > IP Allow.
By default, Neon allows connections from all IP addresses. You only need this step if you have explicitly enabled IP Allow.
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.

​
Neon branches

Neon supports database branching — each branch has its own connection string. When connecting to VexiData, make sure you select the correct branch in the Neon Connection Details widget before copying credentials. If you want to connect multiple branches (e.g., production and staging), create a separate data source in VexiData for each one.

​
Troubleshooting

  • Verify that VexiData’s IP addresses are added to your IP Allow list if the feature is enabled
  • Check that you’re using the correct host — pooled connections include -pooler in the hostname
  • Neon computes auto-suspend after inactivity. The first connection after suspension may take a few seconds to wake up — try again if it times out
  • Double-check your username and password in the Neon Console under Connection Details
  • If you’ve forgotten your password, reset it from the Neon Console
  • Make sure you’re connecting to the correct branch — each branch has its own credentials
  • Confirm your tables are in the public schema. If they’re in a custom schema, update the Schema field in VexiData
  • Check that you selected the correct Database and Branch when copying credentials from Neon
  • Neon’s free tier has compute limits and auto-suspends after 5 minutes of inactivity. The cold start when waking up can cause brief delays
  • Consider upgrading to a paid Neon plan for always-on compute and better performance