First, there was docs.new for instantly creating Google Docs. Then, repo.new made adding new GitHub repositories a breeze. Now, meet pg.new — your gateway to spinning up new Postgres databases in seconds. Simply visit pg.new and you'll be taken straight to the Create project page in the Neon Console, where you can set up your new Neon Postgres project.
Fixes & improvements
Added your current timezone to the Restore branch confirmation page, to make it a little easier to understand the timestamp you are restoring to.
Scale plan users can now view database metrics for the past 14 days on the Monitoring page in the Neon Console. To try it out, go to the Monitoring page and select the Last 14 days item from the Other menu. Previously, metrics could only be viewed for the past 7 days.
The Database size chart on the Monitoring page in the Neon Console now displays size information for up to 10 databases.
Adjusted the functioning of the Create support ticket modal in the Neon Console to avoid automatically selecting Branch and Compute field values when opening the modal.
Fixed an issue that prevented the Autosuspend delay option from being displayed on the Edit compute endpoint drawer in shared projects.
After the next time you log in to Neon Console, navigating to neon.tech will automatically route you to console.neon.tech.
What's new in docs?
We're excited to announce the addition of new Getting Started documentation. If you're new to Neon or want to explore its full range of features, start with these comprehensive guides:
We are excited to announce that Neon has partnered with Neosync to provide developers with a complete solution for branching Postgres databases with anonymized data. Neosync is an open-source platform that helps developers anonymize production data and sync it across their environments for a better developer experience.
Both Neon and Neosync offer generous free tiers. If you’re interested in trying it out, follow the steps in our Neosync guide to get started.
Join the Neon Early Access Program from the Neon Console
You can now join the Neon Early Access Program directly from the Neon Console to be among the first to try new Neon features. From your Profile menu, select Account Settings > Early Access, and submit your Discord username.
The benefits of joining include:
Exclusive early access: Get a first look at upcoming features before they go live.
Private community: Gain access to a dedicated Discord channel to connect with the Neon team and provide feedback to help shape what comes next.
Weekly insights: Receive updates on Neon's latest developments and future plans.
Fixes & improvements
Improved the text on the Billing page in the Neon Console to better explain compute usage and allowances for each of Neon's plans.
Added a Home button to the Neon login page to provide a means of navigating to the Neon website if that was the intended destination.
Updated the Drizzle Studio version that supports the Tables page in the Neon Console. The new version fixes a display issue for long BIGINT values.
Improved the design of Billing summary section on the Billing page in the Neon Console to make it easier to understand your current billing status.
Custom-built extension support is now an Enterprise plan feature only. Any custom-built extensions that we currently support are not affected by this change and will continue to be supported on your current plan.
This new version adds the following features and enhancements:
New vector types: halfvec (up to 4,000 dimensions) and sparsevec (up to 1,000 non-zero elements)
Support for indexing bit type (up to 64,000 dimensions) for binary vectors
Support for quantizing vectors using the binary_quantize function
New distance functions: hamming_distance and jaccard_distance
HNSW indexing for L1 distance operations
Support for CPU dispatching for distance functions on Linux x86-64
For the official list of updates, refer to the pgvector changelog. For documentation related to these new capabilities, please see the pgvector readme.
If you installed this extension previously and want to upgrade to the latest version, please refer to Update an extension version for instructions.
Drizzle Studio in the Neon Console
We're excited to announce that the Tables page in the Neon Console, which lets you explore the tables and data in your Neon databases, is now powered by Drizzle Studio. This integration introduces several new capabilities to the Tables page, including the ability to add, update, and delete records, filter data, add or remove columns, drop or truncate tables, and export data in .json and .csv formats.
Postgres version updates
The Postgres versions supported by Neon have been updated to 14.12, 15.7, and 16.3, respectively.
Fixes & improvements
The Neon CLI connection-string command and the Neon API Get connection URI method now generate a connection URI with a postgresql:// scheme designator instead of the shorter postgres:// designator. While both scheme designators are valid, we found the longer version to be more widely supported.
Added validation for Autosuspend minimum settings. For setting details, see Autosuspend limits.
Added a Charges to date field to the Billing summary section of the Billing page.
You can now access the Edit compute endpoint modal from the Branches widget on the Dashboard by clicking the compute endpoint link.
Fixed an issue on the Branches page that prevented a new branch from being listed immediately after it was created.
Fixed a styling issue that prevented the "Forgot password?" link from being fully visible on the Neon sign-in page while in dark mode.
Improved billing summary
To help you better understand how much your usage is costing in a given billing period, the Billing page now includes a summary detailing your expected costs for that month. This includes the monthly charge for your current plan, as well as any extra charges incurred that month due to peak usage.
All charges are pro-rated. If you upgraded your plan, you only pay the new plan’s rate, prorated from the date you started the new plan within the billing period. Similarly, extra charges are prorated based on the date when your peak usage required any extras. Please note that extra charges do not carry over into the new billing period.
Better copy-connection-to-clipboard action
It's the little things. Since connecting to your database is such an important first step, we've made it that much easier to grab your connection string and go. Previously, the copy-to-clipboard icon was always there, but now, it's explicit: Copy snippet. You can't miss it.
Fixes & improvements
Auth0, Clerk, Okta, Sequin cards on the Integrations page in the Neon Console are now linked to our documentation for those platforms. Clicking on the Read button on the integration card opens a documentation drawer.
Fixed an issue in the SQL Editor that caused it to display a Ready status on page load when the editor was not yet connected. The editor now displays a valid Connected or Ready to connect status.
Fixed an issue that prevented the current endpoint status from displaying properly in the Neon Console.
Fixed an issue that caused changes made in the Edit compute endpoint drawer accessed from the Monitoring widget to disappear after closing and reopening the drawer.
Fixed an issue with the password reveal functionality in the Connection Details widget.
Custom Period Selector for the Monitoring Dashboard
You can now select a custom time period for viewing database metrics on the Monitoring page in the Neon Console. This feature gives you the flexibility of choosing exact start and end dates and times for your monitoring period, helping you with both short-term and long-term trend analysis. To try it out, go to the Monitoring page in the Neon Console and select Custom from the Other menu.
Export query results to CSV, JSON, and XLSX in the Neon SQL Editor
The Neon SQL Editor now supports exporting query results to CSV, JSON, and XLSX formats. Additionally, you can expand your query results view to the entire SQL Editor window. You can access buttons for both features from the bottom right corner of the SQL Editor page.
Fixes & improvements
To make it even easier to try Neon, we've removed the First Name, Last Name, and Password confirmation fields from the Neon Sign Up page. If you're signing up for Neon with an email account, only an email address is required.
Fixed an issue that prevented the current storage usage from being displayed when entering a new billing period, making it appear that storage usage was reset to zero.
Adjusted the location of the Quickstart in the Neon Console and other minor improvements.
A fresh version of the project Quickstart is now available. Use this interactive quickstart as a tutorial to see how branches work to keep your development changes isolated from main, and how easy it is to reset your dev branch whenever you need to.
The Branching workflows tab also gives you a summary of how you can leverage Neon's instant branching in your CI/CD automation.
To launch the Quickstart from the Dashboard, click Show Quickstart at the top of the page.
New Consumption API for accounts
To help Scale plan users get granular consumption metrics for your account as a whole for individual projects, we've added two new endpoints dedicated to the task:
Metrics are available starting March 1st, 2024 for existing Scale plan users. You'll need to specify from and to timestamp parameters that match the selected level of granularity: hourly, daily, or monthly.
Improved navigation for Project pages
We've improved how you move between the different pages in the Neon Console.
The sidebar navigation is re-ordered to help you switch between pages more intuitively.
We moved Operations from a dedicated page to a tab on the Monitoring page called System operations.
Notice that the Compute column is now made up of clickable links, letting you open the side drawer to edit any endpoint's compute settings from this view.
Expect to see more observability-related tabs appear on the Monitoring page in upcoming releases.
Fixes & improvements
We've made it easier for you to properly copy connection strings from the Neon Console. For safety, your password is not revealed directly in the browser but is replaced with ****. When you manually copy the connection string from the text window, the actual password is now included in the clipboard. Previously, copying the connection string directly from the window included the obscured password instead of the actual one.
Using the dedicated copy button continues to work as expected: perfectly!
An issue with the SQL Editor compute endpoint selector has been fixed. The selected endpoint is now correctly used for all of your queries.
When you encounter a project error, you now properly see an error screen. Previously, you were sometimes redirected to the Projects page without adequate explanation.
We fixed an issue where setting the history retention for a Neon project to 0 and removing data did not reduce the project’s storage size as expected. Previously, a 64 MiB data change threshold had to be met before retained history was removed.
Database name validation was added to the Neon CLI connection-string command to ensure the correct database name is used in a generated connection string. This improvement resolves an issue with the neondatabase/create-branch-action GitHub Action, which uses the connection-string command to set the db_url for a newly created branch.
Neon CLI updates
We've added two new capabilities to our CLI:
You can now establish time travel connections to a particular point in a branch's history. When using the neonctl connnection-string {branch} command, simply append the timestamp or LSN to the specified branch and an ephmeral endpoint is created for that point-in-time connection.
The Neon CLI now also includes shared projects when you request a list of all projects using the command neonctl projects list.
Example:
Projects┌────────────────────────┬────────────────────┬───────────────┬──────────────────────┐│ Id │ Name │ Region Id │ Created At │├────────────────────────┼────────────────────┼───────────────┼──────────────────────┤│ crimson-voice-99897020 │ frontend │ aws-us-east-2 │ 2024-04-15T11:17:30Z │├────────────────────────┼────────────────────┼───────────────┼──────────────────────┤│ calm-thunder-11283270 │ backend │ aws-us-east-2 │ 2024-04-10T15:21:01Z │└────────────────────────┴────────────────────┴───────────────┴──────────────────────┘Shared with me┌───────────────────┬────────────────────┬──────────────────┬──────────────────────┐│ Id │ Name │ Region Id │ Created At │├───────────────────┼────────────────────┼──────────────────┼──────────────────────┤│ noisy-fire-516816 │ API │ aws-eu-central-1 │ 2023-04-22T18:41:13Z │└───────────────────┴────────────────────┴──────────────────┴──────────────────────┘
For Launch and Scale plan users, we've added more detail and better visual cues to help you understand your current consumption against your plan's allowances. This includes displaying your peak usage to illustrate any extra charges that might be applied for the current billing period.
Usage widget in the project dashboard
We've also added some polish to the Usage widget on the project dashboard, with tooltips to explain key metrics.
For more information about reading these metrics, see:
Starting May 1, 2024, we're defining 'reasonable usage' for egress on Neon's Free Tier plan as a 5 GB per month limit.
We're updating our status page to provide per-region metrics, letting you view events and history specific to the region where your databases are running. Coming soon!
What's new in docs?
Learn how to sync data from platforms like Stripe, Linear, and GitHub into your Neon database in real time with Sequin.
Neon is Now Generally Available
April 15th, 2024 was a landmark day for us at Neon as we announced our move to General Availability.
Read more about how Neon is transforming database development, supporting business-critical workloads, and innovating in database scaling and branching in the announcement from our CEO, Nikita Shamgunov.
A New Approach to Database Development
Learn about our journey to General Availability and how Neon is redefining database development.
Available from the Neon Console, the Monitoring dashboard provides several graphs to help you monitor both system and database metrics, updated in real time based on your usage data. You can access the Monitoring dashboard from the sidebar in the Neon Console. Metrics include:
We've added a Schema Diff tool that lets you precisely compare database schemas between different branches for better debugging, code review, and team collaboration.
Available from the Branches detail page as well as part of Time Travel Assist from the Restore page, you can use Schema Diff to compare a branch's schema to its parent or compare any two branches during a branch restore operation.
To help with data recovery workflows, we've made our Time Travel feature available in the SQL Editor in the Neon Console. Time Travel Assist is also available now on the Restore page, but it's a great feature and we wanted to make it more convenient for you to use, wherever you might need it in the console.
We added support for psql meta-commands to the SQL Editor in the Neon Console. Meta-commands can significantly speed up your workflow by providing quick access to database schemas and other critical information without needing to write full SQL queries. They are especially useful for database management tasks, making it easier to handle administrative duties directly from the Neon Console.
Here are some of the meta-commands that you can use within the Neon SQL Editor:
\dt — List all tables in the current database.
\d [table_name] — Describe a table's structure.
\l — List all databases.
\? - A cheat sheet of available meta-commands
\h [NAME] - Get help for any Postgres command. For example, try \h SELECT.
Note that not all meta-commands are supported in the SQL Editor. To get a list of supported commands, use \?.
Be among the first to explore new features by signing up for the Neon Early Access Program.
Benefits of joining:
Exclusive early access: Get a first look at upcoming features before they go live.
Private community: Gain access to a dedicated Discord channel to connect with the Neon team and provide feedback to help shape what comes next.
Weekly insights: Receive updates on Neon's latest developments and future plans.
Sign Up Now and start influencing the future of Neon!
Protected branches
Users of the Neon Scale plan can now designate a branch as "protected". This status restricts branch access based on IP addresses — only IPs on your project’s allowlist can access a protected branch. Typically, branches containing production or sensitive data are designated as protected.
For details on configuring a protected branch, please refer to our Protected branches guide.
Large database support (beta)
We are currently testing architecture changes to support large databases from 300 GiB to 2 TiB. Access to this feature is limited to paying users by request. If you want to try it out, you can request access from the Beta tab under Project Settings, or use this direct link:
The JavaScript Registry (JSR) is a package registry for JavaScript and TypeScript. JSR works with many runtimes (Node.js, Deno, browsers, and more) and is backward compatible with npm. For example, to install using npm:
You can now view the last active time for a compute endpoint associated with your branch, which is useful for determining which branches you have accessed recently. In the Neon Console, you can view the Last active time on the Branches page or in the Computes section on individual branch pages. Additionally, the Neon API Get a compute endpoint method response now includes a last_active field.
The Neon SQL Editor now uses the Neon serverless driver for database connections. If you utilize the Neon IP Allow feature and your public IP address isn't currently on the allowlist, you may encounter a pop-up when you next query your database through the Neon SQL Editor. This pop-up requests permission to add your IP address to the allowlist.
Resolved a problem with the Neon Vercel Integration where enabling automatic branch deletion resulted in the unintended removal of the vercel-dev branch after it was renamed.
Resolved an issue where database connections could remain open longer than necessary. We now ensure that connections are forcibly closed if the client has disconnected.
Fixed a table and selector display issue in the Neon console for long branch names.
Fixed an SQL Editor issue that occurred when using the project breadcrumb selector from the SQL Editor page.
Fixed an error in the message displayed after a successful branch reset operation in the console. The "reset from" branch name was not shown.
Fixes & improvements
Based on user feedback, we've changed the Storage metric on the Billing page in the Neon Console to display the current total storage size across all of your projects and branches. Previously, the Storage metric reported the peak storage size for the current billing period.
You can now access integration documentation directly from the Integrations page in the Neon Console. A Read button, available on several integration cards, opens a documentation side drawer where you can learn how to integrate the selected platform or service with Neon.
If you previously signed up for Neon using your Hasura account and now want to use your personal email instead, you can make this change under Profile → Account Settings → Personal Information. You must log out and back into the Neon console before doing so. For more information, see Change your email.
We added a new Restart compute endpoint method to the Neon API. This method suspends the specified compute endpoint and restarts it immediately. It's sometimes necessary to restart a compute endpoint to enable new features or apply new limits. This method makes that task easier and enables us to add a restart compute option to the Neon Console, which you'll see in an upcoming release.
Fixed an issue that prevented preview branches from being shown on the Neon Vercel Integration drawer in the Neon Console.
Added an alert to the Neon Vercel Integration for older Neon projects that do not store role passwords. Neon projects created after March 2023 store role passwords in a secure storage vault associated with the project, allowing passwords to be retrieved from the Connection Details widget and by features such as the Vercel integration that require a password. Projects created before March 2023 do not store role passwords.
Fixed an error message on the Create a new branch page for the Include data up to time selector. The date format in the error message was incorrect.
What's new in docs?
We have three new authentication guides for you to check out this week. Learn how to authenticate users to access your Neon database with Auth0, Clerk, or Okta.
We've added a Monitoring widget to the Neon Dashboard, giving you an easy way to check CPU and RAM usage for your Neon projects. The display defaults to your primary branch but you can switch to view usage details for any branch in your project.
We're committed to improving observability for your Neon projects and databases. To learn more about monitoring in Neon, see Monitoring.
A teaser for organizations
You might notice a new addition to our breadcrumb navigation: Create organization under your account selector. It's greyed out and inactive for now, but we've included it here as a reminder: organization support is coming soon!
Check our roadmap to see what else is coming next.
PostgreSQL Partition Manager extension
Neon now supports the pg_partman partition manager extension, which enables creating and managing time and number-based table partition sets in Postgres.
Local File Cache (LFC) statistics and working set size function
You can now view Local File Cache (LFC) statistics for your Neon compute. The statistics include a cache hit ratio, which can help you determine if your data is being accessed from memory or the Neon storage layer.
The Local File Cache (LFC) stores frequently accessed data in the local memory of your Neon compute instance, which helps reduce latency and improve query performance by minimizing fetches from storage. The LFC acts as an add-on or extension of Postgres shared_buffers, which is set to 128 MB in Neon, regardless of compute size. The LFC extends cache memory to as much as 80% of your compute's RAM.
Local File Cache (LFC) statistics are exposed through a neon_stat_file_cache view, provided by the neon extension. To access the view, install the neon extension on a preferred database or connect to the Neon-managed postgres database where it's preinstalled. For instructions, see The neon extension.
You can retrieve LFC stats with the following query:
