In Neon, you can provision Postgres databases in < 1s. Don't believe us? Check out this demo

Neon Serverless Postgres is Live

No more waitlist. Try Neon now.

Post image

We are very excited to announce that Neon has dropped its invite gate and is releasing its database branching feature. You no longer need to wait for an invite code to try serverless Postgres with Neon — sign up with your Google or GitHub account, and you can be up and running with serverless Postgres in seconds! 

We have a generous free tier for you with availability in four major regions: US West, US East, Europe, and Asia Pacific. Here is what else you get with Neon:

  • 1 Neon project
  • 10 database branches for your production, development, and testing environments, with a limit of 3 GB of data per branch
  • 3 compute instances, each with 1 vCPU and up to 4GB of RAM
  • A point-in-time reset (PITR) window of 7 days of reasonable usage
  • An API to manage your projects, branches, and databases

Sign up now!

Here are a few steps to get you started:

  1. Create a project in seconds and connect to your application with the database URL. 
  2. Query a Neon project database from the Neon SQL Editor or connect using Neon’s passwordless connect feature from your terminal: psql -h
  3. Navigate to the Branches page to create a branch
  4. Import your Postgres data to Neon

With Neon database branching, your database environments are just a branch of your production database. Because Neon stores Write-Ahead-Log records, this means you can create a branch with the latest and most up-to-date information or from any point in time in your database’s history to run tests on the previous state of your data. Read the full announcement in the Database Branching with Neon blog post, or learn more about database branching in the Neon documentation.

You can automate your processes with the Neon API. Create an API Key to manage your projects, branches, and databases with a simple API call from your application or CI/CD. Create a branch, run your tests, then delete it once your jobs are completed. 

curl -X 'GET' \
  '' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer API_KEY'

Join us tomorrow at the Neon Developer Days to talk about All-Things-Branching, where we will discuss using the Neon API for local development and CI/CD with GitHub Actions. Learn more about the Neon API in our documentation.

As always, the Neon team values your feedback, and we’re here to answer your questions. Please get in touch with us in our Community Forum or email us at You can also star Neon on GitHub and find us on Twitter @neondatabase.