Providers / Neon

Databases

Neon API keys and credentials

What every Neon credential a founder holds does, whether it expires, and what tends to break. Each fact links to Neon's own docs.

Last checked 2026-11-06 · neon.com

At a glance

Each credential

API key (personal, organization, or project-scoped)

• Doesn't expire
• Can be scoped

Docs state keys remain valid until revoked and do not expire or rotate on a schedule; rotation is manual. Scope is by level only: personal (the user's access across org projects), organization (all projects, admins only), or single project (admins only, Editor access on that project, cannot delete the project or manage its access). Key value is shown once at creation. Revoke in Console (Account settings > API keys), with `neon api-keys revoke <key-id>`, or DELETE /api/v2/api_keys/{key_id}; revocation is immediate and permanent.

Neon docs

Neon Auth API key (beta SDK)

• You choose
• Expiry readable by API

Separate from the core Neon API. The SDK type reference shows an optional expiresAt field and an isValid() check (not expired and not revoked). Default and maximum durations were not found.

Neon docs

Postgres role password

• Not documented

Reset from Console (role menu > Reset password), CLI (`neon roles reset-password <role>`), the API reset endpoint, or SQL (ALTER ROLE ... WITH PASSWORD). Resets apply per branch; reset the role on each branch where it is used. The old password stops working on the next connection, so connection strings must be updated. Docs do not say whether passwords expire automatically or can be scheduled.

Neon docs

Neon Console login

• Not documented

Console sign-in. Not an API credential. Session policy not researched.

What usually goes wrong

• Postgres role password reset in one branch while another branch still uses the old connection string, so that branch's app fails to connect
• Long-lived API key committed to a repo or CI config; keys do not expire, so a leak stays valid until someone revokes it
• Project-scoped key used for an operation that needs organization-level access

Renewals and billing

• Neon plan. Plan and billing cadence not researched.

Not researched.

What Neon's docs don't say

We couldn't confirm these from official docs, so don't rely on them either way:

• Whether API key expiry is returned by list endpoints
• Finer-grained API key permissions beyond the three levels
• Whether Postgres role passwords can expire automatically or be scheduled
• Neon Auth API key default and maximum durations (only the SDK type reference was seen, not a duration policy)
• Console login and session policy
• Billing model, usage API, and plan cadence

Rotating or replacing a Neon key

The steps are the same for most providers: make the new key, deploy it everywhere the old one is used, check it works, then revoke the old one. Our guides walk through it:

Sources

• neon.com/docs/manage/api-keys
• neon.com/docs/manage/roles
• neon.com/docs/neon-auth/sdk/react/types/api-key

Related providers

Keep track of every Neon key

StackHangar stores your Neon keys in an encrypted vault, grouped by the product they belong to, warns you before they expire, and walks you through rotating them. We can't read your secrets.