OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 10.0/10
Queryable database or replicated schema
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Neon provides Postgres SQL access to a selected branch, database and role. Connection strings can target pooled or direct connections.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Bulk delivery 10.0/10
Customer-initiated native snapshot or full scoped table export
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Use pg_dump against an unpooled connection to retain a standard custom-format Postgres archive.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Query expressiveness 10.0/10
SQL or equivalent joins and aggregations against the operational system
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Run parameterized Postgres queries using the selected database role; platform API keys are a separate credential surface.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Access cost barrier -
-
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The console issues a connection string containing role, password, host and database. Choose the branch and role explicitly and use TLS.
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
Downstream permission -
-
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 10.0/10
Customer-configurable write interfaces with validation
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The Postgres connection supports application SQL within the role’s grants. Schema and data access remain permission-scoped.
Neon PostgreSQL INSERT ↗
INSERT syntax and RETURNING · Checked 2026-10-22
Custom application path 10.0/10
Customer-configurable interfaces for custom applications
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Limit visibility -
-
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 10.0/10
Database extract delivered to the customer
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Neon Postgres connections and query clients ↗
Connection strings, role selection and parameterized queries · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
Planned migration fidelity 10.0/10
Original objects or native schema/data with a documented independent restore/use path
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
The official guide pairs a custom-format pg_dump with pg_restore on a Postgres destination. Check destination versions, extensions, roles and network requirements; this excludes Neon control-plane configuration.
Neon Postgres-compatible export and restore ↗
Export steps on Neon and Restore on your destination · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
Rights to custom logic -
-
Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Neon Postgres connections and query clients ↗
Get a connection string from the Neon console · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
The console issues a connection string containing role, password, host and database. Choose the branch and role explicitly and use TLS.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Use pg_dump against an unpooled connection to retain a standard custom-format Postgres archive. Run parameterized Postgres queries using the selected database role; platform API keys are a separate credential surface.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Postgres branch SQL and pg_dump/pg_restore export | database credentials | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The Postgres connection supports application SQL within the role’s grants. Schema and data access remain permission-scoped.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
The official guide pairs a custom-format pg_dump with pg_restore on a Postgres destination. Check destination versions, extensions, roles and network requirements; this excludes Neon control-plane configuration.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Queryable database or replicated schemaNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Neon provides Postgres SQL access to a selected branch, database and role. Connection strings can target pooled or direct connections. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Customer-initiated native snapshot or full scoped table exportNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Use pg_dump against an unpooled connection to retain a standard custom-format Postgres archive. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | SQL or equivalent joins and aggregations against the operational systemNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Run parameterized Postgres queries using the selected database role; platform API keys are a separate credential surface. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The console issues a connection string containing role, password, host and database. Choose the branch and role explicitly and use TLS. | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| Which external write operations are documented? | Customer-configurable write interfaces with validationNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The Postgres connection supports application SQL within the role’s grants. Schema and data access remain permission-scoped. | Neon PostgreSQL INSERT ↗INSERT syntax and RETURNINGChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer-configurable interfaces for custom applicationsNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| How are integration limits disclosed? | -Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Database extract delivered to the customerNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Neon Postgres connections and query clients ↗Connection strings, role selection and parameterized queriesChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Original objects or native schema/data with a documented independent restore/use pathNeon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. The official guide pairs a custom-format pg_dump with pg_restore on a Postgres destination. Check destination versions, extensions, roles and network requirements; this excludes Neon control-plane configuration. | Neon Postgres-compatible export and restore ↗Export steps on Neon and Restore on your destinationChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Neon / Postgres branch SQL and pg_dump/pg_restore export; platform control-plane configuration, object storage and other Neon products are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Neon Postgres connections and query clients ↗Get a connection string from the Neon consoleChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.