Neon

Deployments fail with a "startTransaction type mismatch" error when using Neon 1.0.0 with Prisma 6.5.0, blocking developers from shipping applications.

Neon's Node.js SDK v19+ introduces a breaking change in how the HTTP query template function can be called. Calling it as a conventional function (with parentheses) is now an SQL injection risk and throws an error, requiring developers to update their applications.

Neon lacked strong limits on the number of branches per project and per customer. Agentic AI systems creating thousands of branches as 'savepoints' overwhelmed the control plane metadata handling system. The absence of rate limiting at test boundaries allowed production workloads to diverge significantly from tested scenarios.

Neon's test suites were designed around historical usage patterns and didn't simulate highly skewed project-to-branch ratios created by agentic AI workloads. Testing at 5x normal load proved insufficient when production experienced 50x load with different distribution characteristics, leading to issues only surfacing in production.

Concurrent API operations within a Neon project on different branches could trigger a "project already has running operations" error, where one branch operation would block others. While concurrency limits have been increased, developers still need to implement retry functionality to handle rare failures.

The Neon Model Context Protocol (MCP) describe_table_schema function does not work correctly with tables using CamelCase naming conventions, limiting schema introspection capabilities.

Neon's re-architected PostgreSQL separates compute and storage into a networked system. This architectural change introduces new performance and latency challenges that developers must understand and mitigate compared to traditional monolithic PostgreSQL.

Neon projects are limited to a single region, which may not meet global application latency requirements and forces developers to choose between regional proximity and using Neon.

Developers must implement strategies to manage and clean up unused database branches to avoid unnecessary storage costs, adding operational overhead to Neon projects.