Release notes

What's new

• Control Plane: The PostgreSQL max_connections setting is now set according to your compute size. Previously, the max_connections setting was 100. The formula that calculates the max_connections setting is RAM in bytes / 9531392 bytes. For example, a compute with 12 GB of RAM has a max_connections setting of 1351. You can check the max_connections setting by running SHOW max_connections; from the Neon SQL Editor or from a client connected to Neon. When Autoscaling is enabled, max_connections is calculated based on the minimum compute size in your Autoscaling configuration.

  Neon supports up to 10,000 simultaneous connections when using connection pooling.

• UI: Updated the Request Downgrade modal on the Billing page for Neon Pro accounts. The button label was changed, the screen height was adjusted, and other stylistic changes were applied.

What's new

• Control Plane: Neon's Autoscaling feature now supports fractional (1/4 and 1/2) minimum compute sizes. Previously, the minimum compute size for Autoscaling was 1. Autoscaling is a Neon Pro plan feature. For configuration instructions, see Compute size and Autoscaling configuration.
• UI: Added a Billing page to the Neon Console where Free Tier users can view Free Tier limits and learn about the benefits of upgrading to the Neon Pro plan. The Billing page is accessible from the sidebar in the Neon Console.
• UI: Implemented minor copy, stylistic, and functional improvements for the Request Downgrade modal accessed from the Billing page.

Bug fixes

• API: Disabled docker as a compute provisioning option in the Neon Create project and Create endpoint APIs. This option is not supported with the Neon cloud service.

What's new

• Control Plane: Project limit checks are now performed for the Neon project owner rather than the currently logged in user. This change enables project limits to be checked against Pro plan limits rather than Free Tier limits when a Free Tier user accesses a project shared by a Pro plan user.
• Control Plane: Newly created Neon projects in a particular region are now assigned Pageservers through a random selection process, which is weighted according to Pageserver free space.
• Control Plane: Removed an unnecessary fetch of project parameters by the Activity Monitor.
• UI: Implemented usability improvements for modals. The changes ensure that modals receive focus when opened and that modal buttons are disabled until there is a valid change and while a form is being submitted. New error messages were also added.
• UI: Improved the hover effect when hovering over steps in the onboarding section on the Neon Dashboard.

Bug fixes

• API: The Update endpoint API now permits moving an endpoint from one branch to another without specifying autoscaling_limit_max_cu and autoscaling_limit_min_cu property values, which should not be required when performing this action.
• Control Plane: Neon plan limits are now transmitted when using passwordless authentication, enabling users logging in via this method to create projects, in accordance with their plan limits.
• UI: Fixed an issue that prevented Free Tier users from creating a compute endpoint for an existing branch. The Fixed size compute setting in the Create Compute Endpoint modal defaulted to 1 vCPU, which exceeded the Free Tier compute size limit.
• UI: Fixed the Auto-suspend delay control on the Create Compute Endpoint and Edit Compute Endpoint modals to permit values up to 604800 seconds (7 days). The limit was recently increased from 86400 seconds (1 day).
• UI: Fixed issues with how icons were displayed in the Usage widget on the Neon Dashboard.

What's new

• UI: Adjusted how Autoscaling minimum and maximum compute sizes are displayed in the Compute endpoints table on the branch details page.
• UI: Added a History retention metric to the Storage widget on the Neon Dashboard. By default, Neon retains a 7-day history of data changes to support point-in-time restore. History retention will become a configurable setting in a future release.
• UI: Enhanced the Request Downgrade modal, which is accessible from the Billing page in the console. Downgrading from Neon's Pro plan back to the Free Tier is now a fully automated and instant process. This change eliminates the previously required step of sending a downgrade request to Neon support.
• Control Plane: Adjusted the time interval for measuring compute utilization in Neon to avoid rounding decisions and ensure accuracy for fractional compute sizes.

Bug fixes

• UI: Fixed modals in the console to enable form submission when the Enter key is pressed.
• UI: Fixed submission buttons that remained enabled after being clicked and while form data was being submitted.

What's new

• Control Plane: Added support for configuring the PostgreSQL default_text_search_config configuration parameter, which determines the behavior of text search functions and operators that do not have an explicit configuration. This parameter can be set for the PostgreSQL instance using the default_endpoint_settings property in the Create project or Update project API, or using the pg_settings property in the Create endpoint or Update endpoint API. Alternatively, the parameter can be set for a specific database using ALTER DATABASE syntax:

  ALTER DATABASE <dbname> SET default_text_search_config = ‘pg_catalog.english’;

• Control Plane: Implemented a ClusterIP service to be used instead of the existing NodePort service to support a higher number of simultaneously running computes in a single region.

• UI: Added Pooled connection and Direct connection tabs to the Connection Details widget on the Neon Dashboard, allowing you to copy a pooled or direct connection string for the selected branch, database, and role.

What's new

• API: Enabled checking for the Neon API specification to ensure that examples are updated when the specification is modified.

• API: Added a history_retention_seconds property to the Project response body. Neon retains a 7-day history to support point-in-time restore. History retention will become a configurable parameter in a future release.

• API: Increased the maximum value of the suspend_timeout_seconds property in the Endpoint API from 86400 seconds (1 day) to 604800 seconds (7 days). This change affects the maximum Auto-suspend delay setting that Neon Pro plan users can configure when creating or editing a compute endpoint. The Auto-suspend delay setting defines the number of seconds of inactivity after which a compute endpoint is automatically suspended. The default is 300 seconds (5 minutes). For more information, see Auto-suspend configuration.

• UI: Redesigned the branch details page in the Neon Console. In addition to the information displayed previously, the page now provide usage metrics, including Active time, Compute time, Written data, and Data transfer. This information enables you to monitor usage for individual branches. Refer to the Billing section for information about the usage metrics.

  The compute endpoint information on the branch details page has also been expanded to include Compute size, Auto-suspend delay, and Last active information. Compute size (min) and Compute size (max) values are shown for computes with the Autoscaling feature enabled. For information about these values, see View a compute endpoint.

• UI: Added an Active time column to the table on the Branches page in the Neon Console. This column shows the number of hours the branch compute endpoint has been active for the current month.

• UI: The Connection Details dialog displayed when creating a project or a branch now provides Pooled connection and Direct connection tabs, allowing you to copy a pooled or direct connection string for the default neondb database. For information about connection pooling in Neon, see Connection pooling.

• UI: Updated the prisma.js code example accessible from the Connection Details widget on the Neon Dashboard. The connection string now includes a connect_timeout parameter to prevent Prisma from timing out due to cold starts, and a pgbouncer=true parameter, which is required when using Prisma with a pooled connection string. For more information about using Neon with Prisma, see Connect Neon to Prisma.

• Control Plane: Added a constraint to ensure that the maximum Autoscaling compute size is greater than or equal to the minimum compute size.

• UI: Added icons and hover help to the Usage widget on the Neon Console.

What's new

• Control Plane: Added support for the timescaledb extension, which scales PostgreSQL for time-series data. For more information about PostgreSQL extensions supported by Neon, see PostgreSQL extensions.
• UI: Added hover help to the PRIMARY branch badge that identifies a branch as the primary branch for a project. The help message states that the compute endpoint associated with the primary branch remains accessible if you exceed project limits, ensuring uninterrupted access to the data on your primary branch.

Bug fixes

• UI: Fixed the Neon Project Creation dialog to display a value for the Fixed Size compute option. A value was not displayed previously.
• UI: Fixed the Create Compute Endpoint and Edit Compute Endpoint dialogs to enable switching between Fixed Size and Autoscaling compute options, enabling you to configure the compute size for each compute endpoint individually. For information about Neon's Autoscaling feature, see Autoscaling.
• UI: Fixed the Edit Compute Endpoint dialog so that the Autoscaling compute provisioning slider does not permit selecting unsupported minimum values. The minimum compute size for Autoscaling is 1 vCPU and 4 GB of RAM.
• UI: Fixed an issue that caused text on the Neon Dashboard to overflow when reducing the size of the browser window.

What's new

• API: Added consumption_period_start and consumption_period_end properties to the Get project details API. These properties provide the date and time when Neon starts and stops measuring usage for the current billing period.
• Control Plane: Added support for the pg_stat_statements extension, which provides tracking of plan and execution statistics for SQL statements. For more information about PostgreSQL extensions supported by Neon, see PostgreSQL extensions.
• Control Plane: Added an option to allow the Neon Control Plane to provide a compute node configuration specification in an API call after a compute node is started.
• Integrations: Added information to the Neon Vercel Integration UI to indicate that Neon securely stores passwords. Neon stores a database user's password in a secure storage vault associated with the Neon project.
• UI: You can now configure the period of inactivity after which a compute is automatically suspended by modifying the Auto-suspend delay setting for a compute endpoint. For example, you can increase the Auto-suspend delay setting to reduce how often a compute is suspended, or you can disable the Auto-suspend feature entirely to ensure that a compute remains active. The maximum Auto-suspend delay setting is 86400 seconds (24-hours). A setting of 0 means use the default (5 minutes / 300 seconds), and a setting of -1 means never suspend the compute. You can access the configuration dialog by editing a compute endpoint.
• UI: Added a Storage widget to the Neon Dashboard that shows current project storage size, number of branches, and data size for the primary branch. These metrics previously appeared in the Usage widget.
• UI: Removed the previously deprecated Pooler enabled option from the Edit Compute Endpoint dialog. Connection pooling is now enabled for individual connection strings instead of compute endpoints. For more information, see Connection pooling.
• UI: The Usage widget in the Neon Dashboard now shows the start date for the project usage metrics shown in the widget.
• UI: Added a link to the Pro badge that appears in the Neon Console for users that have upgraded to Neon's Pro plan. Clicking the badge directs you to the Billing page in the Neon Console.
• UI: Added a documentation link and text to the Roles page in the Neon Console explaining the purpose of roles.
• UI: Added hover help to the PRIMARY branch badge that identifies a branch as the primary branch for a project. The help message states that the compute endpoint associated with the primary branch remains accessible if you exceed project limits, ensuring uninterrupted access to the data on your primary branch.

Bug fixes

• API: Project limits for shared projects are now checked against the project owner's limits. Previously, limits were checked against the project user's limits, which could prevent a Free Tier user from making full use of a project shared by a Pro plan user.
• UI: Corrected an issue that directed users to a Something went wrong page after creating a branch without a compute endpoint.
• UI: Added missing endpoint_id to the connection examples accessible from the Connection Details widget on the Neon Dashboard.

What's new

• API: Added a branch object to the Create project endpoint that allows you to specify names for the primary branch, role, and database created with a project. Previously, specifying non-default names for these objects required additional API calls after creating a project.
• API: Updated the List project consumption endpoint description to indicate that the pagination maximum is 1000.
• Control Plane: Added an option to enable a foreground deletion policy for Kubernetes clusters, which blocks other operations until cascading resource deletions are finished. The foreground option reduces the amount of polling for operation completion.
• Control Plane: Added the ability to search for branches in S3 storage, enabling identification of branches in storage that have already been deleted in the console.
• Control Plane: Simplified SQL logging to reduce the amount of log write processing.

What's new

• UI: Designating a different branch as the primary branch of a Neon project is now supported. The compute endpoint associated with the primary branch remains accessible if you exceed project limits, ensuring uninterrupted access to data on the primary branch. You can designate a new primary branch by selecting a branch from the Branches page in the Neon console and clicking Set as primary.
• UI: A Beta version of Neon's Autoscaling feature is now available for paid plan users in selected regions. Autoscaling allows you to specify a minimum and maximum compute size. Neon scales compute resources up and down within the specified compute size boundaries to meet workload demand. The Autoscaling feature can be enabled when creating a Neon project or by editing a compute endpoint.
• Integrations: The Neon Vercel Integration no longer resets the password of the Neon role (the Neon database user). Previously, the password was reset to enable the integration to configure Vercel environment variables that require a password. Neon now stores passwords in a secure storage vault associated with the Neon project, allowing existing passwords to be retrieved.
• Control Plane: Free Tier compute endpoints are now assigned 0.25 Compute Units (CU) by default, which is equal 0.25 vCPUs and 1 GB of RAM.

Deprecated

• API: Removed the quota_reset_at property from the Project consumption endpoint used by Neon partners. The property did not provide useful data.

What's new

• UI: Adjusted the text in the Usage widget on the Neon Dashboard that describes the expected delay time for usage metrics.
• UI: Adjusted the Project storage metric labels in the Usage widget to identify one as Project storage (usage), which is a measure of monthly storage in GiB-hrs, and the other as Project storage (size), which is a measure of the current data size.
• UI: Revised the subscription cancellation warning on the Billing page.
• UI: Updated text and links in the Neon onboarding banner in the Neon Console.
• UI: Updated the Docs link in the Neon Console sidebar to point to the new documentation landing page.

What's new

• API: Updated the region_id description in the Project API to include a link to the list of regions supported by Neon.
• UI: Revised the style of the Unsubscribe dialog accessed from the Billing page in the Neon Console.
• UI: Updated the metric units in the Usage widget on the Neon Dashboard

Bug fixes

• UI: Fixed an issue that prevented Usage widget metrics on the Neon Dashboard from displaying data as expected. The API that supports the widget did not provide the required data.
• UI: Fixed an issue that caused Free Tier usage to be included in metrics data displayed in the Usage widget on the Neon Dashboard after upgrading to the Neon Pro plan. This issue did not affect billing.

What's new

• API: Added a suspend_timeout_seconds property to the Endpoint API, which specifies the duration of inactivity (in seconds) after which a compute endpoint is automatically suspended.
• UI: Added support for fractional Compute Units (CU), enabling configuration of compute endpoints with a quarter or half CU. One CU has 1 vCPU and 4 GB of RAM.
• UI: Adjusted the labels and text on the Edit Compute Endpoint dialog.
• UI: Added support for Pro Plan customers to change payment details. Payment details can be changed by editing the Payment method on the Billing page in the Neon Console.
• UI: Added a Request subscription cancellation button to the Billing page in the Neon Console, which opens an Unsubscribe dialog. Customers can use the dialog to submit a plan cancellation request.
• UI: Revised the cancellation warning on the Billing page in the Neon Console.
• UI: Added a safety limit of 20 active compute endpoints. When the limit is exceeded, an endpoint is created but not activated.
• UI: When creating a branch, a complete connection string with the user name, password, and database name is now provided in the Connection Details dialog that is shown after branch creation.
• UI: Added a Usage widget to the Neon Dashboard for monitoring project usage. The usage widget tracks metrics such as Active time, Compute time, Project storage, Branches, and Current data size.
• UI: Added more domains to the console's Content Security Policy (CSP) HTTP response headers to enhance Neon Console security. CSP headers provide an additional layer of security for web pages by allowing a website to control what resources (such as scripts, stylesheets, and images) can be loaded and executed on its pages.

What's new

• API: Removed the physical_size property from the Branch response body in the Neon API.
• UI: Changed the User label on the Connection Details widget to Roles. Database users are now referred to as Roles in Neon.
• UI: Added descriptive text and a documentation link to the Integrations page in the Neon Console.
• UI: Added support for sharing projects with other Neon users. Project sharing is performed from the Settings page in the Neon Console. The project sharing feature is available only to Neon paid plan users, but projects can be shared with any Neon user, including Free Tier users. For instructions, see Manage projects.
• UI: Added an Upgrade to Pro option to the Neon Console to enable upgrading from Free Tier to Neon's Pro plan. For information about Neon's paid plans, please refer to Billing.

Bug Fixes

• Control Plane: Addressed a memory leak that affected Neon Console performance. A memory limit was put in place prevent similar issues.
• UI: Fixed the connection examples accessible from the Connection Details widget on the Neon Dashboard. Examples other than the psql example had an extra project name in the connection hostname.
• UI: Fixed the "Manage" link on the Branches widget on the Neon Dashboard. The link did not work.

What's new

• UI: Updated the labels, links, and units shown on the Project limits widget on the Neon Dashboard.

Bug Fixes

• API: Adjusted the tags in the Neon API specification that assign endpoints to categories. The new Neon API reference displays one endpoint per page. Multiple tags assigned to an endpoint resulted in endpoints not being listed under their primary category.
• UI: Fixed the vertical alignment of buttons on authorization dialogs.
• UI: Removed a newline character from the connection string in the connection details dialog that is displayed after creating a new project.

What's new

• API: A new cpu_used_sec property was added to the Project response body in the Neon API. This property shows the number of CPU seconds used by a branch's compute endpoints. The value resets to zero at the beginning of each billing period.
• Control Plane: By default, Neon suspends a compute endpoint after five minutes of inactivity. A custom configuration option was added to enable configuring or disabling the suspension threshold for compute endpoints. Disabling the threshold allows a compute endpoint to remain active indefinitely, which avoids latencies associated with restarting idle compute endpoints. This feature is not yet generally available. You can expect it to be introduced with Neon paid tiers.
• UI: New Neon projects now store role passwords in a secure storage vault associated with the project, allowing passwords to be retrieved from the Connection Details widget on the Neon Dashboard. Secure password storage reduces the need for password resets and facilitates the use of Neon features that require a password. The stored passwords feature is not yet available for existing Neon projects.
• UI: New Neon projects no longer include the system-managed web_access role. This role was used by the Neon SQL Editor and passwordless auth feature. With the introduction of stored passwords, the web_access role is no longer required. Removal of the web_access role also addresses permission issues encountered when attempting to perform actions as the web_access role on objects owned by other roles or vice versa.

What's new

• API: The connection_uris property in the Create branch response is no longer a required property, meaning that the field is not included in the response if the value is empty. The connection_uris property is now returned only in cases where a branch has only a single database and role.

• API: Added property descriptions for Project, Branch, Endpoint, Database, Role, and Operation endpoints.

• Control Plane: A compute endpoint now remains in an active state after resetting a password, creating a role, or creating a database. Previously, a compute endpoint was suspended following those actions. This behavior caused unnecessary latency when accessing the compute endpoint immediately afterward. The latency was due to the few seconds required to restart the compute endpoint.

• UI: The Neon Free Tier now includes a compute endpoint with each branch. Previously, there was a limit of 3 endpoints per project. This limit was removed based on user feedback indicating that it was not conducive to developer workflows that create a branch for each preview deployment.

  Instead of limiting the number of endpoint computes in the Neon Free Tier, there is now a limit of 100 compute active time hours per month. Currently, the compute hour limit applies to newly created projects only. The limit does not yet apply to existing projects. We expect to apply the limit to all projects later this quarter. Regardless of the compute hour limit, you are always able to connect to the compute endpoint associated with the primary branch of your Neon project. For more information, see Technical Preview Free Tier.

  If you have any questions about how this change to Neon's Free Tier limits might impact your existing project, please contact us at support@neon.tech.

• UI: With the removal of the endpoint limit, endpoints no longer appear in the Project limits widget on the Neon Dashboard.

• UI: With the introduction of pooled connections strings (see Enable pooling), enabling pooling for a compute endpoint is deprecated. With this change, the Pooler enabled toggle on the Edit Compute Endpoint dialog is now disabled and will be removed in a future release.

• UI: Changed a column heading in the table on the Operations page from ID to Action. The items listed in the column are operation actions rather than IDs.

• UI: Renamed the Users page in the Neon Console to Roles. This change aligns Neon's terminology with PostgreSQL, which uses the concept of "roles" to refer to database users. (See Database roles, in the PostgreSQL documentation.) All UI elements in the Neon Console were updated to reflect this change.

• Integrations: Improved text and fixed a documentation link in the Neon Vercel Integration UI.

What's new

• Control Plane: Increased the PgBouncer maximum client connection setting from 1000 to 10000, enabling Neon to support up to 10000 simultaneous connections. For more information about connection pooling in Neon, see Connection pooling.
• Control Plane: Added an internal retry mechanism for connections to the Neon proxy, which improves the success rate for connection attempts. The Neon proxy is a service that accepts and handles connections from clients that use the PostgreSQL protocol.
• UI: Added Content-Security-Policy (CSP) HTTP response headers to enhance Neon Console security. CSP headers provide an additional layer of security for web pages by allowing a website to control what resources (such as scripts, stylesheets, and images) can be loaded and executed on its pages.

Bug fixes

• API: The Neon API specification now shows the default (10) and maximum (100) pagination values for the List projects API endpoint. These settings were enforced previously but were not included in the Neon API specification.
• API: Updating a project name resulted in the loss of values defined in default_endpoint_settings property, which defines custom settings for project's compute endpoints.
• Control Plane: A chain of operations failed to run in the expected order due to a lock related issue. In addition to operations running out of sequence, some operations were executed more than once.

What's new

• API: Added a quota_reset_at property to the Project response schema in the Neon API. This property displays a future date indicating when a resource consumption quota will be reset. For example, the Neon Free Tier offers 100 compute hours per month. The quota_reset_at property shows when that quota will be set back to 100 hours.
• API: Added a compute_seconds_limit property to the CurrentUserInfoResponse schema in the Neon API. This property defines the monthly compute limit in terms of compute seconds.

Bug fixes

• Integrations: The Neon integration with Vercel did not create branches for preview deployments when the Vercel user ID differed from the one specified when adding the Neon integration to Vercel. This issue was encountered when using the Neon integration from a Vercel Teams account.

What's new

• UI: Updated various UI elements in the Neon Console to rename Endpoints to Compute endpoints. The term Endpoint was not specific enough to accurately reflect the resource being referred to. A Compute endpoint in Neon refers the compute instance that runs PostgreSQL.
• UI: Added a PRIMARY badge to identify the primary branch of a Neon project. The badge is visible on the Branches page in the Neon Console and in other UI elements that show a project's branches.
• API: The default_endpoint_settings property in the Project schema was split into default_endpoint_settings and settings. The default_endpoint_settings property is now used exclusively for PostgreSQL specific settings applied to a project's compute endpoints. The settings property is used for general project settings such as the compute quota. If you have been using createProject or updateProject API requests in your code, you may need to update those requests to account for this change.

What's new

• Integrations: You can now integrate Neon with your Vercel project directly from your Vercel account. The new integration, which is currently in Beta, is available from the Vercel Integration Marketplace. The integration allows you to connect your Vercel project to a new or existing Neon project. It also enables creating a database branch for each Vercel preview deployment and for your Vercel development environment. For more information about the Neon-Vercel integration, see Connect Vercel and Neon.

• Control Plane: You can now enable connection pooling in Neon for individual connections. Pooling is enabled by adding a -pooler suffix to the endpoint ID in the Neon hostname. For example:

  postgres://sally@ep-square-sea-260584-pooler.us-east-2.aws.neon.tech/neondb
  

  Connections that do not specify the -pooler suffix connect to the database directly. The ability to enable pooling for individual connections supports workflows that require both pooled and non-pooled connections to the same database. For example, serverless applications that use Prisma Client require a pooled connection, while Prisma Migrate requires a direct connection to the database. For more information, see Enable connection pooling.

  The previous method of enabling connection pooling for a compute endpoint is deprecated. When switching to the new per-connection method, be sure to disable connection pooling at the compute endpoint. You can do so by editing the compute endpoint.

• UI: With the removal of the endpoint limit, endpoints no longer appear in the Project limits widget on the Neon Dashboard.

Bug fixes

• Console: Added validation to ensure that emails are provided in the expected format when creating a Neon account.
• Control Plane: Added validation for the Log Sequence Number (LSN) provided when creating a branch from a particular LSN value to prevent the possibility of creating a branch from an unrelated parent branch. An appropriate error is now reported when an invalid LSN value is provided.

What's new

• API: The response body for projects, branches, and endpoints now exposes a creation_source property. Currently, the creation_source property identifies the console as the creation source in all cases but will eventually identify other sources, such as the Neon API.
• API: Listing projects with the Neon API now supports cursor-based pagination. Pagination enables limiting the number of responses displayed at one time, which is useful when a response includes a large number of projects. By default, the first 10 projects are returned. You can set the limit parameter to request up to 100 projects.
• Control Plane: Added support for OpenTelemetry for a number of operations. OpenTelemetry is an observability framework that assists in generating and capturing telemetry data from cloud-native software.
• Control Plane: Removed the stop_compute operation, which is no longer used. It was replaced by suspend_compute.
• UI: Revised the layout of the Neon Console to improve navigation. The following enhancements were implemented:
  • A new sidebar with icons replaces the navigation bar that was located at the top of the console.
  • Operations, Databases, and Users pages, previously accessed from the Settings page, are now directly accessible from the sidebar.
  • Links to Community, Feedback, Docs, Release notes, and Support, previously located in a Help menu in the navigation bar, were moved to the sidebar for easier access.
  • The Neon account avatar was moved from the top right corner of the console to the sidebar.

Bug fixes

• API: Fixed a race condition that occurred when creating a project and attempting to fetch information about branch in the same project.
• Control Plane: Fixed a cannot execute GRANT in a read-only error that occurred when a database owner enabled the default_transaction_read_only setting, preventing the Control Plane from configuring the compute instance.
• UI: Fixed the positioning of selection menus in the console to avoid scrolling outside intended boundaries.

What's New

• UI: Added a Pooler enabled toggle control to the Edit endpoint dialog to permit enabling or disabling connection pooling for endpoint compute instances. The same control is available on the Create endpoint dialog. Previously, connection pooling was enabled or disabled for a project, and the control was located in Settings > General. Connection pooling is disabled, by default. For more information about Neon's connection pooling feature, see Connection pooling.
• UI: Completed the migration of the Neon Console from Neon API v1 to Neon API v2. The Neon API v1 is deprecated.
• UI: Added a Region column to the Projects dialog in the Neon Console to show the region where a Neon project resides.
• UI: Improved WebSockets integration with the Neon Console, and added Websocket support for endpoint updates.
• API: Added a branch_logical_size_limit attribute to the Neon API Project response body, which shows the logical data size limit for project branches. This attribute replaces the logical_size_limit attribute, which was shown in the Branch response body. The Neon Free Tier limits the logical data size of a branch to 3072MB (3GB).
• API: Added the ability to delete or reassign the endpoint associated with a project's root branch. Previously, these actions could not be performed on the endpoint associated with a project's root branch. You can edit or delete an endpoint by selecting Edit or Delete from the kebab menu in the table on the Endpoints page.
• API: Updated descriptions and examples in the Neon API v2 reference.
• Control Plane: Migrated older branches that were created using the Neon API v1 to their parent project. Branches created with Neon API v1 existed as separate Neon projects. After the migration, the branches exist as Neon API v2 branch and endpoint objects that belong to a parent project. Connection strings for migrated branches, which use the old project_id in the hostname, are no longer valid. Instead of the project_id, an endpoint_id must be specified in the hostname. For information about constructing a valid connection string, see Connect from any application. An email with migration instructions was sent to affected users.

Bug Fixes

• UI: Passwords are now temporarily displayed in the Connection Details widget on the project Dashboard after project creation and password reset operations. The password is displayed until you navigate away from the Neon Console or refresh the browser.
• API: Added validation to ensure that the name specified when creating a role does not exceed 63 bytes. Role names longer than 63 bytes caused compute startup issues.

What's New

• Control Plane: Neon now attempts to deploy compute resources in the same availability zone as the Pageserver.
• API: The request body for the create branch API is now optional. Previously, a request body with branch or endpoints attributes was required. Without a request body, the default behavior is to create a branch from the project's root branch (main) without an endpoint, and the branch name is auto-generated.

Bug Fixes

• UI: Removed the password from the connection string that is displayed in the Connection Details widget on the Neon Dashboard after project creation. A connection string and .env file with the password are provided in a pop-up dialog after creating a project.
• UI: Neon's passwordless auth feature no longer requires selecting an endpoint for projects with a single endpoint.

What's new

• API: Added request and response body examples to the Neon API v2 specification.
• API: Disabled deleting or changing the endpoint compute instance associated with a project's root branch.
• API: Added a logical_size_limit attribute to the branch schema, which shows the data size limit for a branch.
• API: Renamed the max_project_size attribute in Neon API v1 specification to branch_logical_size_limit.
• API: Removed the max_project_size attribute from Neon v2 API schema.
• Control Plane: Implemented a forced suspension of endpoints that are unresponsive for more than 2 hours.
• UI: Removed the Neon invite gate. An invitation is no longer required to try Neon. It is available to everyone. For more information, refer to the Neon is Live! blog post.
• UI: Released the Neon database branching feature. Branching is now available to all users. For more information, refer to the Database Branching for Postgres with Neon blog post.
• UI: Added new and improved popup dialogs for project, branch, and role creation.
• UI: Added an Endpoints page to the Neon Console for creating and managing endpoints, which are the compute resources in your Neon project. For more information about endpoints, see Endpoints.
• UI: Enabled creating branches with data up to a specified Log Sequence Number (LSN).
• UI: Updated the passwordless auth feature to show the branch name on the browser page that is displayed during authentication.
• UI: Updated the Create branch page to display the local timezone when selecting the Time option during branch creation.
• UI: Removed branches without endpoints from the branch selector in Neon SQL Editor. To query a branch, the branch must have an associated endpoint through which a connection can be established.
• UI: Added a Free tier widget to the Neon Dashboard, which shows how many branches and endpoints you have created and the status of your free tier limits. The widget also shows the data size limit per branch, which is 3GB. For information about Free Tier limits, see Neon Technical Preview Free Tier.

Bug fixes

• API: Fixed a project duplication issue in the list projects method in the Neon API v1.
• Control Plane: Improved the reliability of the passwordless auth feature.
• Control Plane: Fixed an issue that caused an endpoint to be created in a region other than the project's region.
• UI: Enabled reset password functionality for non-root branches.

What's new

• API: Creating branches using the Neon API v1 is now deprecated.
• API: Added support for cursor pagination when listing operations.
• API: Added validation for empty names to branch and project endpoints.
• API: Added LSN validation to the create branch endpoint.
• API: Made the parent_id and name attributes optional when creating a branch.
• API: Added a complete endpoint hostname value in the endpoint response body.
• API: Added support for changing the branch of an endpoint.
• API: Added an allow_connections flag for endpoints to permit disabling connections to the endpoint.
• API: Added support for creating a branch without an endpoint, which is now the default if the endpoints attribute is not specified. Creating a branch without an endpoint supports backup uses cases and useful in scenarios where the number of branches exceeds the number of available endpoints due to endpoint limits.
• API: Added response examples to the API specification.
• API: Create project and create endpoints now treat the region_id parameter as region.id. The attribute was previously treated as region.handle. Code that uses these endpoints may need to be updated.
• Control Plane: Renamed the default database created in the root branch of a Neon project from main to neondb.
• Control Plane: Added new autoscaling limits.
• Control Plane: Added a project maintenance flag.
• Control Plane: Added a region maintenance and testing flag.
• UI: Added a branch ID value and Create branch button to the branch details page in the console.
• UI: Updated the Neon Free Tier limits. See Technical Preview Free Tier for details. The new Neon Free Tier limits apply to both new and existing projects, but the previous 10 GB storage limit will be honored for existing projects that currently have more than 3 GB of data.
• UI: Added a Delete endpoint button to the Endpoints page.
• UI: Updated the Neon passwordless auth feature to select an endpoint to connect to instead of a project.

Bug fixes

• API: Fixed the ordering of operations and projects.
• API: Corrected the error reported when a duplicate branch name is used.
• Control Plane: Added handling for ID collisions when creating a branch or endpoint.
• UI: Fixed an endpoint polling issue.
• UI: Stopped polling when deleting a project.
• UI: Added handling for errors that occur when polling endpoint status.
• UI: Removed visibility of internal service roles.
• UI: Added handling for sign-in during passwordless auth.
• UI: Fixed the NodeJS connection string example in the Connection Details widget on the Dashboard.

What's new

• UI: Postgres 15 is now the default version when creating a Neon project.
• UI: Added support for renaming branches. To rename a branch, select the branch on the Branches page in the Neon Console and click Rename branch.
• UI: Added TIME and LSN fields to the branch details page for child branches. The TIME field shows the time value selected when creating a branch with data up to a specified point in time. The LSN field shows a Log Sequence Number (LSN), indicating that the branch was created with data up to that LSN.
• UI: Added a branch icon to the branch selection menu on the Databases and Users pages in the Neon Console.
• UI: Added badges for various elements on the branch details page in the Neon Console.
• Control Plane: Introduced a maintenance mode for Neon projects. When a project is placed into maintenance mode, its endpoints are forcibly suspended and modifications are not permitted until maintenance is completed.
• Control Plane: Added support for Cross-Origin Resource Sharing (CORS) to the Neon API v1 and v2.
• Control Plane: Added descriptions for endpoint categories to the Neon API v2, and changed the ApiKey tag to API Key.
• Control Plane: Added the ability to fetch all endpoints for a specified branch to the Neon API v2. Thank you to our Neon community member for the feature request.
• Control Plane: Added the ability to create endpoints without specifying an instance ID to the Neon API v2.
• Control Plane: Added the ability to retrieve information about the current user to the Neon API v2. User details such as login, email, and other parameters specified in the OpenAPI specification can now be retrieved.

Bug fixes

• UI: Fixed an issue that prevented project and endpoint statuses from being updated when making changes.
• Control Plane: Added a "Content-Type" header with an "application/json" value to Neon API v2 error responses.
• Control Plane: Fixed a memory leak that occurred when handling SQL requests.
• Control Plane: Improved diagnostic information by extracting error messages from Pageserver responses during project creation.
• Control Plane: Stopped manually rolling back the current transaction when the user cancels the context. The Go driver ConnBeginTx interface performs this operation automatically.

What's new

• UI: Added support for the US East (Ohio), Europe (Frankfurt), and Asia Pacific (Singapore) regions, allowing you to create Neon projects closer to your application servers. For more information about Neon's region support, see Regions.

• UI: Updated Neon's branching capabilities. The following enhancements were introduced:

  • Added a Branches page to the Neon Console for creating and managing branches.
  • Each project now has a root branch called main.
  • Branches now belong to a project. You can create a branch from your project's root branch (main) or from another branch in the project.
  • You can now define the data to include in a branch. You can include all data up to the current point in time or up to a past point in time.
  • Each branch is now created with a named endpoint, which is the compute instance associated with a branch. Connecting to a branch requires connecting to the branch's endpoint. You can obtain a connection string for a branch endpoint from the Connection Details widget on the Neon Dashboard.

  For more information about Neon's branching capabilities, see Branching, and Get started with branching.

  Neon Branching capabilities are not yet publicly available. If you would like to try this feature, contact us at iwantbranching@neon.tech, describing your use case and requesting that Neon enable branching for your account.

• UI: With the addition of support for new regions and updates to Neon's branching capabilities, changes were made to the hostname in Neon connection strings. Previously, a hostname had this format: <project_id>.cloud.neon.tech. With the introduction of new regions, a <region_slug> and <platform> value were added to the hostname for projects created in newly supported regions. With the update to branching capabilities, <project_id> was replaced by <endpoint_id>. As a result of these changes:

  • Projects created in the original Neon region, US West (Oregon), have this hostname format: <endpoint_id>.cloud.neon.tech.
  • Projects created in the newly supported regions, have this hostname format: <endpoint_id>.<region_slug>.<platform>.neon.tech.

  The old hostname format continues to be supported for projects created before these changes were introduced.

• UI: Added highlighting support for PostgreSQL 15 SQL Keywords to Neon's SQL Editor. Keywords are highlighted when entered in the SQL Editor.

• UI: Added the ability to display the navigation bar at the top of the Neon Console as a side drawer menu on small screens.

Bug fixes

• UI: Fixed an issue in the SQL Editor that prevented errors from being reported when rerunning multi-statement queries.
• UI: Updated the .pgpass configuration instructions provided after creating a project or resetting a password. The instructions did not include the required PostgreSQL port number.
• Control Plane: Improved handling of OAuth consent challenges. A user is now directed to the destination URL to complete the login or consent request instead of receiving a 410 Gone error when resubmitting an OAuth consent challenge.
• Control Plane: Fixed memory leaks that could occur for background operations started in a context that does not expire. An operation failure could have resulted in resources not being cleaned up.

What's new

• Integrations: Added OAuth support for Hasura users, enabling seamless authentication with Neon from Hasura Cloud. To learn more about connecting from Hasura Cloud to Neon, see Connect from Hasura Cloud to Neon.

Bug fixes

• UI: The Database drop-down menu in the Connection Details widget on the Dashboard and in the Neon SQL Editor now permits selecting any created database.
• Control Plane: The availability checker now waits for the project operations queue to clear before starting.
• Control Plane: Operations for redo are now selected based on the correct status.
• Control Plane: The V2 branch creation endpoint is now accessible using an OAuth token.

What's new

• Integrations: Added read, update, delete project access scopes for OAuth applications.
• Integrations: Added the ability to select access scopes and projects on the OAuth consent page.
• API: Added a protected: boolean flag to the roles public API response.
• API: Changed region and platform ids from serial numbers to strings in the public API.
• API: Changed the operations id from a serial number to a UUID type in the public API.
• Control Plane: Added an internal mechanism for relocating projects between Pageservers.
• Control Plane: Stopped sending metrics to Grafana Cloud.
• Control Plane: Removed usage of the obsolete zenith_ctl binary.
• Control Plane: Split the monolithic project object into project, branches, and endpoints in the internal database schema.

Bug fixes

• UI: Fixed a failure that occurred after receiving an empty response in the SQL Editor.
• UI: Fixed an issue to ensure that table names are reset when switching between schemas on the Tables page in the Neon Console.
• Control Plane: Fixed a passwordless auth issue that occurred when creating a new project using the project selection interface.

What's new

• UI: Added functionality that enables providing an OAuth app name to a client.

Bug fixes

• UI: Fixed the title on the 'Sign in' page.
• UI: Changed the PostgreSQL version displayed on the project dashboard to 14.5.
• Control Plane: Fixed authentication of concurrent proxy connections to an idle compute node. Previously, one of the concurrent proxy connection attempts would fail with a Failed to connect to the compute node error.

What's new

• Control Plane: Implemented OAuth backend support and OAuth consent screens, which enable granting OAuth applications permission to create projects on behalf of users. Services interested in OAuth integration with Neon should contact partnerships@neon.tech.

Bug fixes

• UI: Fixed the syntax highlighting for Golang snippets.
• UI: Fixed styles for smaller screens.

What's new

• UI: Added a Submit Feedback feedback form to the Neon Console. The form is accessible from the Help menu.

Bug fixes

• UI: Fixed a CORS error for API requests in the Swagger UI. The error occurred when using the 'Try it out' feature.

What's new

• UI: Added a Tables page to the Neon Console for viewing database schemas and tables. Drop-down menus permit navigating between project databases. Table data can be viewed by selecting the table from the sidebar.
• UI: Added a Help menu to the Neon Console which provides links to various user assistance resources.
• Control Plane: Added the ability to select Safekeepers from different availability zones for new projects.

Bug fixes

• UI: Fixed the .pgpass password file instructions that are presented when resetting a password #1825.
• UI: Added validation messages to the Project Creation dialog.
• UI: Fixed broken links in the Neon onboarding section of the Neon Console.
• UI: Updated the email addresses presented in the UI for requesting branching capabilities and support. The email address for requesting access to branching is iwantbranching@neon.tech. The email address to request support is support@neon.tech.

What's new

• UI: The Neon SQL Editor now maintains a history of previously executed queries and permits saving queries. For more information about these capabilities, see Query with Neon's SQL Editor.
• UI: Added token-based authorization to the Swagger UI for Neon's public API.
• UI: Changed the display status of operations waiting in the queue from In progress to Scheduling.
• UI: Disabled controls that incorrectly remained enabled while the Neon project was in a transitive state.
• Control Plane: Set max_replication_write_lag to 15 MB to tune the backpressure mechanism and improve PostgresSQL responsiveness under load.
• Control Plane: Improved the ability to investigate performance issues by collecting and saving more detailed compute node startup time metrics.

Bug fixes

• UI: Fixed incorrect encoding when switching between code samples in the Connection Details widget on the project Dashboard, and added descriptions to connection string examples.
• UI: Fixed various typos and errors.

Bug fixes

• UI: Fixed an issue that prevented project status updates from being communicated to the Neon Console. Prior to this fix, the previous project status was reflected in the Neon Console until the page was reloaded.

What's new

• UI: Added validation to ensure that the API key Name field is not left blank when creating a new API Key on the Developer Settings page. For information about API keys, see Manage keys.
• UI: Added a Create branch button to the project Dashboard for selected users. To request early access to Neon branching capabilities, send an email to iwantbranching@neon.tech.
• UI: Added a detailed error message to the Neon SQL Editor for failed queries.
• Control Plane: Added a new version of the operations executor that includes various stability and observability improvements.
• Control Plane: Compute node logs are now dumped if the startup process fails.
• Control Plane: Added support for deleting timeline data from all storage nodes (Safekeepers and Pageserver) after project deletion.

What's new

• UI: Added an Enable pooling toggle to the project General setting page, which permits enabling or disabling connection pooling for a project. For more information about Neon connection pooling support, see Connection pooling.
• Control plane: Implemented the usage of several instances for serving the public API and web UI to enable zero-downtime deployments.
• API: Changed the error reported when a concurrent operation on a project prevents acquiring a project lock. Error 423 Locked is now reported instead of 409 Conflict.

What's new

• Control Plane: Implemented connection pooling support for Neon projects, allowing Neon to support a greater number of connections. For information about enabling connection pooling for a Neon project, see Connection pooling.
• API: Added a pooler_enabled property to the project update API call to indicate whether or not connection pooling is enabled.

Bug fixes

• API: Fixed several bugs that could cause intermittent 409 responses, which indicate a request conflict with the current state of the target resource.

What's new

• UI: The Neon Technical Preview invite code is now requested only at the first login.
• UI: Added a cover to password fields to protect passwords from view. Passwords are presented to users after performing actions such as creating a project, creating a user, or resetting a password.
• API: Changed the user_id type from int64 to uuid.
• API: Implemented a unified JSON error response where possible, in the format of { "message": "error text" }.
• API: Made platform, region, and instance_type ids optional during new project creation.

Bug fixes

• Control Plane: Fixed an issue that allowed the web_access system role to be modified or deleted, which could affect the functioning of the Neon SQL Editor.