# Neon Postgres

Managed Postgres with branching and optional pgvector.

## Comparison target

Relational / Vector · Cloud DBaaS · Managed service

Neon hosted Postgres; vector claims require enabling pgvector per database. Other backend services are excluded.

Components: postgresql

Revision: 2026-09-14.1 · Review: unreviewed

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

## Applicability

Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.. Neon hosted Postgres; vector claims require enabling pgvector per database. Other backend services are excluded..

## Claims

- **yes · documented**: Provides hosted Postgres. [Neon documentation](https://neon.com/docs/introduction.md) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Offers serverless managed Postgres. [Neon documentation](https://neon.com/docs/introduction.md) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Supports database branching. [Neon documentation](https://neon.com/docs/introduction.md) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Provides compute autoscaling and scale to zero. [Neon documentation](https://neon.com/docs/introduction.md) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Documents instant restore. [Neon documentation](https://neon.com/docs/introduction.md) Scope: Restore window and availability depend on configuration and plan.
- **yes · documented**: Supports vector similarity with pgvector enabled. [Neon pgvector](https://neon.com/docs/extensions/pgvector.md) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Supports HNSW and IVFFlat through pgvector. [Neon pgvector](https://neon.com/docs/extensions/pgvector.md) Scope: Documented for this target; no runtime tests recorded.

## Open questions

- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?

## Verification plan

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Last checked: 2026-09-14. Recheck by: 2026-10-14.

Content rights: Unlicensed prototype; redistribution decision pending.