The latest product updates from Neon
RSS feed
default_pool_size limit from 16 to 64 to prevent running out of available server connections. This limit defines the number of server connections allowed per user/database pair.connection_timeout parameter or shadowDatabaseUrl variable. These are no longer required due to reduced Neon cold start times and support for database creation via SQL.DISABLE_SERVER_SIDE_CURSORS to true when using a pooled connection.We streamlined the connection snippets in the Connection Details panel for better usability:
sslmode=require, enabling encryption by default.These changes apply wherever the Connection Details pane appears: on the Dashboard page, when you create a branch, and when you create a project.
Neon now supports email authentication, enabling users to sign up for Neon using a personal or business email account. Previously, you could only sign up with a GitHub or Google account.
To sign up with an email account, navigate to https://console.neon.tech, select the Email option, and click Sign up for an account. You will be directed to the Sign up dialog.
We enhanced our onboarding experience for Neon Free Tier users with a redesigned user interface. Create a Neon project with a Postgres database in seconds.
UI: Added new fields for configuring the auto-suspend delay period for Neon compute instances, allowing you to specify the delay period in seconds, minutes, hours, or days.
Neon's Auto-suspend feature automatically suspends a compute endpoint after a period of inactivity to minimize compute costs. This feature is also known as "scale-to-zero". By default, suspension occurs after 5 minutes of inactivity. Neon Pro Plan users can configure the auto-suspend setting when creating a project, changing default compute settings, creating a compute endpoint, or editing a compute endpoint.
For more information about this feature, see Auto-suspend.
UI: When sharing a Neon project with someone who does not have a Neon account, an email invitation is now sent to the specified email address. Previously, an email was only sent to registered Neon users.
Project sharing is a Neon Pro Plan feature that allows you to share your project with other Neon accounts. For more information, see Project sharing.
UI: Updated PostgreSQL 14 and 15 keyword highlighting in the Neon SQL Editor, and addressed other syntax highlighting and autocompletion issues.
relation does not exist error when viewing table data in a database and then selecting a different database.Pro plan users can now configure default compute settings for a Neon project. Settings include Compute size, Autoscaling, and Auto-suspend delay. To define defaults, select Settings > Compute from the Neon Dashboard to open the Default compute settings page. For Free Tier users, the page shows the default settings.
Default settings are applied when creating a branch or adding a compute to a branch via the Neon Console. However, if you want a compute with different settings, you can change or override the defaults when creating a branch or adding a compute.
In addition, the Compute widget on the Neon Dashboard now shows the Default compute size for your Neon project.
You can now configure the history retention period for a Neon project. History retention enables point-in-time restore, allowing you to restore data to any point within the retention period. By default, Neon retains a 7-day history of data changes for all branches. The supported history retention range is 0 to 7 days for Free Tier users, and 0 to 30 days for Pro plan users.
The History retention setting is located in the Neon Console under Settings > Storage.
After an extensive testing period, we are pleased to announce that our Configurable auto-suspend feature has successfully transitioned out of Beta. This feature controls when a Neon compute instance scales to zero due to inactivity. For more information, see Configuring Auto-suspend for Neon computes.
API: The Create branch API method now creates a branch from the project's primary branch if a parent_id is not provided in the create branch request.
API: Deprecated the pooler_enabled attribute in the Create endpoint API method. This attribute is no longer required, as you can now enable connection pooling by adding a -pooler flag to a database connection string. See Enable connection pooling.
UI: The Compute widget on the Neon Dashboard now displays the Active computes limit for your Neon project. There is a default limit of 20 simultaneously active computes to protect Neon accounts from unintended or unexpected usage. Neon Pro plan users can have the limit increased by submitting a request to our support team.
UI: Fixed an issue on the Downgrade dialog accessible from the Neon Pro plan Billing page that prevented selecting a reason for downgrading.
UI: Fixed dark theme styling issues.
Neon's Auto-suspend feature scales a compute instance to zero after a period of inactivity. A characteristic of this feature is a "cold start", which occurs when an idle compute is restarted to process requests. Recently, cold-start times have been improved through a variety of enhancements, outlined below:
With these improvements, cold starts are faster in all supported regions. Cold starts in the US East (Ohio) — aws-us-east-2 region, where the Neon Control Plane is hosted, are the fastest at approximately 500 ms. Work is underway to deploy the Neon Control Plane regionally to enable the same millisecond startup times for projects in all regions. For more information about this effort, please check out the blog post from the Neon engineering team: Cold starts just got hot.
Please be aware that Neon Pro plan users can adjust or disable the Auto-suspend setting, controlling when a compute scales to zero. Additionally, Neon's Autoscaling feature allows you to scale compute resources down to a fractional size during periods of low activity.
Neon now provides an Auto-suspend delay control on the project creation dialog, enabling Neon Pro plan users to define a default Auto-suspend delay setting for a project's compute endpoints. The Auto-suspend delay setting defines the period of inactivity after which a compute endpoint is automatically suspended. For more information, see Create a project.
Neon is pleased to announce the release of the Neon CLI, a command-line interface that enables developers to manage Neon resources directly from the terminal. The Neon CLI supports numerous operations, including creating and managing projects, branches, databases, roles, read replicas, and more, directly from your terminal. You can also use Neon CLI commands in developer workflows and pipelines.
You can install the Neon CLI with a single command:
Homebrew is also supported:
To get started with the Neon CLI, read the blog post or refer to the Neon CLI reference.
Typical use cases and Custom tabs were added to the Pro Plan Cost Estimation tool that is accessible from the Billing page on the Neon Free Tier. This tool helps you estimate what your monthly cost would be if you upgraded to the Neon Pro plan.
suspend_timeout_seconds parameter to the default_endpoint_settings object in the Create project API. This parameter defines the amount of time before the project's default compute endpoint is suspended due to inactivity. The default is 300 seconds (5 minutes).autoscaling_limit_min_cu and autoscaling_limit_min_cu parameters in the Create project project object. You can configure these parameters in the default_endpoint_settings object instead when creating a project.scram-sha-256.server_login_retry setting in PgBouncer's configuration was adjusted to remove any delay between Postgres connection retries.Introduced a Pro Plan Cost Estimation tool designed to assist Free Tier users. This tool provides an estimated cost for the Pro Plan based on your current project usage. If you've ever wondered, "How much would my monthly cost be if I upgraded to the Neon Pro plan today?", this tool provides the answer. To access it, go to the Billing page via the sidebar of the Neon Console and select Estimate costs.
UI: The code examples accessible from the Connect Details widget on the Neon Dashboard now include a -pooler suffix in the endpoint hostname when the Pooled connection tab is selected. You no longer need to add this suffix manually.
UI: - Resolved an issue where the Time field on the Branch details page incorrectly displayed the date after creating a branch from main using the Time option. Now, the field correctly displays the time.
Connection pooling can now be used in combination with the Neon Autoscaling feature. Previously, connection pooling was only available with fixed-size computes.
Neon supports up to 10,000 simultaneous connections when using connection pooling.
The Postgres 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.
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.
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.
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.
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.autoscaling_limit_max_cu and autoscaling_limit_min_cu property values, which should not be required when performing this action.Control Plane: Added support for configuring the Postgres 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 Postgres 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:
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.
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.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.neondb database. For information about connection pooling in Neon, see Connection pooling.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.Added support for the timescaledb extension, which scales Postgres for time-series data. For more information about Postgres extensions supported by Neon, see Postgres extensions.
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.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.
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.
Added support for the pg_stat_statements extension, which provides tracking of plan and execution statistics for SQL statements. For more information about Postgres extensions supported by Neon, see Postgres extensions.
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.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.Something went wrong page after creating a branch without a compute endpoint.endpoint_id to the connection examples accessible from the Connection Details widget on the Neon Dashboard.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.A Beta version of Neon's Autoscaling feature is now available for Pro 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.
quota_reset_at property from the Project consumption endpoint used by Neon partners. The property did not provide useful data.region_id description in the Project API to include a link to the list of regions supported by Neon.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.
suspend_timeout_seconds property to the Endpoint API, which specifies the duration of inactivity (in seconds) after which a compute endpoint is automatically suspended.physical_size property from the Branch response body in the Neon API.psql example had an extra project name in the connection hostname.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.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.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.
Integrations: Improved text and fixed a documentation link in the Neon Vercel Integration UI.
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 reach out to us on the Neon community forum.
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 Postgres, 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.
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.default_endpoint_settings property, which defines custom settings for project's compute endpoints.10000 simultaneous connections. For more information about connection pooling in Neon, see Connection pooling.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.compute_seconds_limit property to the CurrentUserInfoResponse schema in the Neon API. This property defines the monthly compute limit in terms of compute seconds.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 Postgres 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.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.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:
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.
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.
UI: With the removal of the endpoint limit, endpoints no longer appear in the Project limits widget on the Neon Dashboard.
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.limit parameter to request up to 100 projects.stop_compute operation, which is no longer used. It was replaced by suspend_compute.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.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 3072 MiB (3 GiB).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.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..env file with the password are provided in a pop-up dialog after creating a project.logical_size_limit attribute to the branch schema, which shows the data size limit for a branch.max_project_size attribute in Neon API v1 specification to branch_logical_size_limit.max_project_size attribute from Neon v2 API schema.parent_id and name attributes optional when creating a branch.allow_connections flag for endpoints to permit disabling connections to the endpoint.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.region_id parameter as region.id. The attribute was previously treated as region.handle. Code that uses these endpoints may need to be updated.main to neondb.ApiKey tag to API Key."Content-Type" header with an "application/json" value to Neon API v2 error responses.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.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.
Updated Neon's branching capabilities. The following enhancements were introduced:
main.main) or from another branch in the project.For more information about Neon's branching capabilities, see Branching, and Manage branches.
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.
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:
<endpoint_id>.cloud.neon.tech.<endpoint_id>.<region_slug>.<platform>.neon.tech.The old hostname format continues to be supported for projects created before these changes were introduced.
Added highlighting support for Postgres 15 SQL Keywords to Neon's SQL Editor. Keywords are highlighted when entered in the SQL Editor.
410 Gone error when resubmitting an OAuth consent challenge..pgpass configuration instructions provided after creating a project or resetting a password. The instructions did not include the required Postgres port number.protected: boolean flag to the roles public API response.zenith_ctl binary.read, update, delete project access scopes for OAuth applications.Failed to connect to the compute node error..pgpass password file instructions that are presented when resetting a password #1825.max_replication_write_lag to 15 MB to tune the backpressure mechanism and improve PostgresSQL responsiveness under load.In progress to Scheduling.423 Locked is now reported instead of 409 Conflict.pooler_enabled property to the project update API call to indicate whether or not connection pooling is enabled.user_id type from int64 to uuid.{ "message": "error text" }.platform, region, and instance_type ids optional during new project creation.web_access system role to be modified or deleted, which could affect the functioning of the Neon SQL Editor.