> ## Documentation Index
> Fetch the complete documentation index at: https://vexidata.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Neon

> Connect your Neon serverless PostgreSQL database to VexiData.

## Prerequisites

* A [Neon](https://neon.tech) account with an existing project
* A [VexiData](https://vexidata.com) account

## Understanding Neon connection modes

Neon offers two ways to connect — with or without connection pooling. The difference is in the hostname:

|                     | Pooled Connection                              | Direct Connection                       |
| ------------------- | ---------------------------------------------- | --------------------------------------- |
| **Host**            | `ep-[name]-[id]-pooler.[region].aws.neon.tech` | `ep-[name]-[id].[region].aws.neon.tech` |
| **Port**            | `5432`                                         | `5432`                                  |
| **Best for**        | Short-lived, on-demand connections             | Persistent, long-running connections    |
| **How to identify** | Host contains `-pooler`                        | Host does not contain `-pooler`         |

<Tip>
  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.
</Tip>

## Connect Neon to VexiData

<Steps>
  <Step title="Get your Neon connection details">
    1. Log in to your [Neon Console](https://console.neon.tech)
    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:

    | Parameter    | Example                                                |
    | ------------ | ------------------------------------------------------ |
    | **Host**     | `ep-cool-forest-123456-pooler.us-east-2.aws.neon.tech` |
    | **Port**     | `5432`                                                 |
    | **Database** | `neondb`                                               |
    | **Username** | `neondb_owner`                                         |
    | **Password** | Your database password                                 |

    <Info>
      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**.
    </Info>
  </Step>

  <Step title="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**.

    <Info>
      By default, Neon allows connections from all IP addresses. You only need this step if you have explicitly enabled IP Allow.
    </Info>
  </Step>

  <Step title="Add the connection in VexiData">
    1. Go to [Data Sources](https://vexidata.com/data-sources) in VexiData
    2. Click **PostgreSQL** to open the connection form
    3. Fill in the details:

    | Field            | Value                                                                |
    | ---------------- | -------------------------------------------------------------------- |
    | **Display Name** | A name to identify this connection (e.g., "Neon Production")         |
    | **Host**         | `ep-[name]-[id]-pooler.[region].aws.neon.tech`                       |
    | **Port**         | `5432`                                                               |
    | **Database**     | `neondb` (or your database name)                                     |
    | **Schema**       | `public` (default — change if your tables are in a different schema) |
    | **Username**     | Your Neon database username                                          |
    | **Password**     | Your database password                                               |
  </Step>

  <Step title="Test and save">
    Click **Test & Save Connection**. VexiData will verify it can reach your database. Once connected, your schema will be analyzed automatically.
  </Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="Connection timed out">
    * 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
  </Accordion>

  <Accordion title="Authentication failed">
    * 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
  </Accordion>

  <Accordion title="No tables visible after connecting">
    * 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
  </Accordion>

  <Accordion title="Connection drops or is slow">
    * 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
  </Accordion>
</AccordionGroup>