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

# Neon

> Connect a Neon organization to find and create Postgres databases.

Hoista finds the Neon projects in an organization and shows each Postgres database. It can create a new Neon project, and a deploy can create one for your app.

## Connect

Neon connects with an API key:

1. Open [API keys](https://console.neon.tech/app/settings/api-keys): **Account settings → API keys → Create new API key**. Name it Hoista.
2. Copy the key. It starts with `napi_` and Neon shows it once.
3. In Desktop, open **Accounts**, choose Neon, paste the key and pick the organization.

![Neon’s API keys page](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/tokens/neon-token.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=cc17a9d2a1f5d1fa71232a09249957b9)

Neon’s API keys page, captured November 2026. Personal details are blurred. If yours looks different, the names in the steps still match.

From the CLI:

```bash theme={null}
hoist accounts add neon
```

Hoista asks for the key in a hidden prompt and finds the organization from it. In scripts, use `hoist accounts add neon --name NAME --token-stdin`, and add `--account <organization-id>` if the token reaches more than one organization.

## What you can do

* Create a Neon project with a Postgres database.
* Let a deploy plan create the database and pass its connection string to your app as `DATABASE_URL`.
* See compute and data transfer on **Metrics**. Neon keeps this history on paid plans only.
* See the organization's plan usage this month on **Billing**: compute hours, storage and data transfer. This also needs a paid plan.
* Export a database with `hoist db export <resource>`. This needs `pg_dump` where Hoista runs; `hoist tools` shows whether it is found.
* Run Neon's own operations from the **Neon** tab.
* Delete a Neon project after you confirm it by name.

Hoista doesn't read Neon logs.

## Bring in existing resources

Hoista looks for projects when you connect. In Desktop, add them as described in [Bring in an existing project](https://docs.hoista.dev/guides/import-apps.md). From the CLI:

```bash theme={null}
hoist import --list
hoist import <resource-id> --project my-app
```

`--project my-app` adds the database to an existing project. Use `--new <name>` to start a new one. Projects start in **watching** mode. Run `hoist projects manage my-app` when you want Hoista to make changes. To look again, run `hoist accounts refresh <account>` with the name or ID from `hoist accounts`.

## Related

> [card] [Providers](https://docs.hoista.dev/providers/overview.md)
>
> What Hoista supports on each provider.

> [card] [Connect hosting accounts](https://docs.hoista.dev/guides/accounts.md)
>
> Connect, check and rotate accounts.

> [card] [Bring in a project](https://docs.hoista.dev/guides/import-apps.md)
>
> Add what an account already runs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.