[metadata]
description: How to view and modify data in the console Create an isolated database copy per developer Reset your branch to production when ready to start new work About branching Branching workflows Connect Neon ...
og:description: How to view and modify data in the console Create an isolated database copy per developer Reset your branch to production when ready to start new work About branching Branching workflows Connect Neon ...
og:image: https://neon.com/docs/og?title=VG91ciB0aGUgTmVvbiBDb25zb2xl&category=VG91ciB0aGUgTmVvbiBDb25zb2xl
og:site_name: Neon
og:title: Tour the Neon Console - Neon Docs
og:type: article
og:url: https://neon.com/docs/get-started/signing-up
twitter:card: summary_large_image
twitter:description: How to view and modify data in the console Create an isolated database copy per developer Reset your branch to production when ready to start new work About branching Branching workflows Connect Neon ...
twitter:image: https://neon.com/docs/og?title=VG91ciB0aGUgTmVvbiBDb25zb2xl&category=VG91ciB0aGUgTmVvbiBDb25zb2xl
twitter:site: @neondatabase
twitter:title: Tour the Neon Console - Neon Docs
viewport: width=device-width, initial-scale=1, viewport-fit=cover

[canonical-links]
https://neon.com/docs/get-started/signing-up

[document-links]
.NET: /docs/guides/dotnet-npgsql
/docs
AI Gateway: /docs/ai-gateway/overview
AI agents on Neon: /docs/ai/ai-agents-tools
APIs & SDKs: /docs/reference/api
AWS DMS: /docs/import/migrate-aws-dms
About branching: /docs/introduction/branching
About: /about-us
AlloyDB: /docs/guides/logical-replication-alloydb
Apache Software Foundation: https://www.apache.org
Astro: /docs/guides/astro
Auth: /docs/auth/overview
Azure regions deprecation: /docs/import/azure-regions-deprecation
Azure: /docs/import/migrate-from-azure-postgres
Better Drizzle: /docs/guides/better-drizzle
Blog: /blog
Branch reset: /docs/guides/reset-from-parent
Branching workflows: /docs/get-started/workflow-primer
Building on Neon: /docs/guides/platform-integration-overview
Built to scale: /docs/get-started/built-to-scale
Bun: /docs/guides/bun
CCPA Compliant: https://trust.neon.com/?itemUid=4064ac33-7b48-407b-aed7-ce02971d1ec1
CSV: /docs/import/import-from-csv
California Privacy: https://www.databricks.com/legal/supplemental-privacy-notice-california-residents
Careers: https://www.databricks.com/company/careers/open-positions?department=engineering&location=all&itm_source=www&itm_category=company&itm_page=engineering-at-databricks&itm_location=body&itm_component=hero&itm_offer=open-positions
Changelog: /docs/changelog
Cloud SQL: /docs/guides/logical-replication-cloud-sql
Community Guides: /guides
Community: /docs/community/community-intro
Compliance Guide: /docs/security/hipaa
Connect Neon to your stack: /docs/get-started/connect-neon
Connecting Neon to your tools: /docs/get-started/connect-neon
Contact Sales: /contact-sales
Data API: /docs/data-api/overview
Developer experience: /docs/get-started/dev-experience
Digital Ocean: /docs/import/migrate-from-digital-ocean
Discord Server: https://discord.gg/92vNTzKDGp
Discord: https://discord.gg/92vNTzKDGp
Django (Django ORM): /docs/guides/django
Docs: /docs
Drizzle Studio: https://orm.drizzle.team/drizzle-studio/overview
Drizzle: /docs/guides/drizzle
Drizzle: https://drizzle.team/
Edit on GitHub: https://github.com/neondatabase/website/tree/main/content/docs/get-started/signing-up.md
Elixir Ecto: /docs/guides/elixir-ecto
Elixir: /docs/guides/elixir
Encore: /docs/guides/encore
Entity Framework: /docs/guides/dotnet-entity-framework
Examples repo: https://github.com/neondatabase/examples
Explain and Analyze: /docs/get-started/query-with-neon-sql-editor#explain-and-analyze
Express: /docs/guides/express
FAQs: /faqs
Firebase: /docs/import/migrate-from-firebase
Frameworks: /docs/get-started/frameworks
Full backend quickstart: /docs/get-started/full-backend-quickstart
GDPR Compliant: https://trust.neon.com/?itemUid=45220873-6e51-4dbb-b1b1-37d66ee9ef95
Get started: /docs/introduction
GitHub: https://github.com/neondatabase/neon
Glossary: /docs/reference/glossary
Go: /docs/guides/go
HIPAA Compliant: /docs/security/hipaa
Heroku: /docs/import/migrate-from-heroku
Hono: /docs/guides/hono
ISO 27001 Certified: https://trust.neon.com/?itemUid=1fed9faa-4a87-427c-9a95-96b4d6bf66b7
ISO 27701 Certified: https://trust.neon.com/?itemUid=dc79cbc7-c99d-4eb9-891e-f5dc44b943d7
Import Data Assistant: /docs/import/import-data-assistant
Integrations & tooling: /docs/guides/integrations
Invite members: /docs/manage/orgs-manage#invite-members
Java: /docs/guides/java
JavaScript: /docs/guides/javascript
Knex: /docs/guides/knex
Kysely: /docs/guides/kysely
Languages: /docs/get-started/languages
Laravel (Eloquent): /docs/guides/laravel
Learn PostgreSQL: https://neon.com/postgresql/tutorial
LinkedIn: https://www.linkedin.com/company/neon-inc/
Log in: https://console.neon.tech/login
MSSQL: /docs/import/migrate-mssql
Manage & operate: /docs/manage/platform
Managed Better Auth quickstarts: /docs/auth/overview
Managed Better Auth: /docs/auth/overview
Managing your data with interactive tables: /docs/guides/tables
Medusa.js: /docs/guides/medusajs
Micronaut Kotlin: /docs/guides/micronaut-kotlin
Modern Slavery Statement: https://www.databricks.com/legal/modern-slavery-policy-statement
MySQL: /docs/import/migrate-mysql
Neon Docs: /docs/introduction
Neon Functions: /docs/compute/functions/overview
Neon Platform Terms: /platform-terms
Neon SQL Editor: /docs/get-started/query-with-neon-sql-editor
Neon plans: /docs/introduction/plans
Neon status loading...: https://neonstatus.com/
Neon to Lakebase: /docs/guides/migrate-neon-to-lakebase
Neon to Neon: /docs/guides/logical-replication-neon-to-neon
Neon to Neon: /docs/import/migrate-from-neon
Neon to another region: /docs/import/migrate-neon-to-another-region
Neon: /
Neon’s Sub Contractors: /hipaa-contractors
NestJS: /docs/guides/nestjs
Next Frameworks: /docs/get-started/frameworks
Next.js: /docs/guides/nextjs
Node.js: /docs/guides/node
Nuxt: /docs/guides/nuxt
ORMs: /docs/get-started/orms
Object Storage: /docs/storage/overview
One-command setup: /docs/get-started/with-an-agent
Our mission: /docs/get-started/why-neon
Overview: /docs/import/migrate-intro
Overview: /docs/import/region-migration
Phoenix: /docs/guides/phoenix
PlanetScale: /docs/import/migrate-from-planetscale
Plans & billing: /docs/introduction/about-billing
PostgreSQL Tutorial: /postgresql/tutorial
Postgres-compatible export: /docs/guides/export-neon-postgres-compatible
Postgres: /docs/guides/logical-replication-postgres-to-neon
Postgres: /docs/postgres/overview
Previous Tour the Neon backend: /docs/get-started/backend-overview
Prisma: /docs/guides/prisma
Prisma: https://www.prisma.io/
Privacy Notice: https://www.databricks.com/legal/privacynotice
Python: /docs/guides/python
Quarkus (JDBC): /docs/guides/quarkus-jdbc
Quarkus (Reactive): /docs/guides/quarkus-reactive
RDS: /docs/guides/logical-replication-rds-to-neon
RSS feeds: /docs/reference/feeds
Railway: /docs/import/migrate-from-railway
React Router: /docs/guides/react-router
React: /docs/guides/react
RedwoodSDK: /docs/guides/redwoodsdk
Reflex: /docs/guides/reflex
Remix: /docs/guides/remix
Render: /docs/import/migrate-from-render
Resilience & architecture: /docs/introduction/architecture-overview
Roadmap: /docs/introduction/roadmap
Ruby on Rails (ActiveRecord): /docs/guides/ruby-on-rails
Rust: /docs/guides/rust
SOC 2 Certified: https://trust.neon.com/?itemUid=7bfa66da-33ab-49de-8391-e329738a1ae9
SQL Editor documentation: /docs/get-started/query-with-neon-sql-editor#ai-features
SQLAlchemy: /docs/guides/sqlalchemy
SQLite: /docs/import/migrate-sqlite
Sample data: /docs/import/import-sample-data
Scale to zero: /docs/introduction/scale-to-zero
Schema Diff: /docs/guides/schema-diff
Schema-only: /docs/import/migrate-schema-only
Security & compliance: /docs/security/security-overview
Security: /security
Set up Managed Better Auth: /docs/auth/overview
Sign up: https://console.neon.tech/signup
SolidStart: /docs/guides/solid-start
Startups: /startups
Status: /docs/introduction/status
Supabase: /docs/guides/logical-replication-supabase-to-neon
Supabase: /docs/import/migrate-from-supabase
Support: /docs/introduction/support
Sveltekit: /docs/guides/sveltekit
Symfony: /docs/guides/symfony
Terms of Use: https://www.databricks.com/legal/terms-of-use
Time Travel: /docs/guides/time-travel-assist
Tortoise ORM: /docs/guides/tortoise-orm
Tour the Neon Console: /docs/get-started/signing-up
Tour the Neon backend: /docs/get-started/backend-overview
Trust Center: https://trust.neon.com
Turso: /docs/import/migrate-from-turso
TypeORM: /docs/guides/typeorm
Vue: /docs/guides/vue
X.com: https://twitter.com/neondatabase/
You can now deploy Neon Functions - they live in the branch next to your DB, are long-running, perfect for agents and realtime: https://neon.com/blog/neon-functions-backend-logic-next-to-your-data
YouTube: https://www.youtube.com/channel/UCoMzQTJSIr7-RU1QbomQI2w
branch: /docs/introduction/branching
expire and be deleted: /docs/guides/branch-expiration
https://console.neon.tech/signup: https://console.neon.tech/signup
https://discord.gg/92vNTzKDGp
https://github.com/neondatabase/neon
https://neon.com/docs/llms.txt: https://neon.com/docs/llms.txt
pg_dump / pg_restore: /docs/import/migrate-from-postgres
pgcopydb: /docs/import/pgcopydb
schema-only branching: /docs/guides/branching-schema-only
set-context: /docs/cli/set-context

[structured-data]
{"@context":"https://schema.org","@type":"Article","author":{"@type":"Organization","name":"Neon"},"headline":"Tour the Neon Console"}

[content]
Tour the Neon Console - Neon Docs
You can now deploy Neon Functions - they live in the branch next to your DB, are long-running, perfect for agents and realtime
Neon
Docs
Search
...
⌘K
Ask AI
Log in
Sign up
Get started
Products
Postgres
Auth
Data API
Neon Functions
Object Storage
AI Gateway
Platform
Manage & operate
Resilience & architecture
Security & compliance
Plans & billing
Building on Neon
AI agents on Neon
Reference
APIs & SDKs
Integrations & tooling
Glossary
Resources
Support & Community
Support
Community
Product updates
Status
Changelog
Roadmap
RSS feeds
Starter code
Examples repo
Learn PostgreSQL
Search
...
⌘K
Ask AI
Full Neon documentation index:
https://neon.com/docs/llms.txt
Neon Docs
Why Neon?
Our mission
Developer experience
Built to scale
Start with Neon
One-command setup
Full backend quickstart
Tour the Neon backend
Tour the Neon Console
Frontend & Frameworks
Frameworks
Astro
Bun
Entity Framework
Encore
Express
Medusa.js
Micronaut Kotlin
NestJS
Next.js
Node.js
Nuxt
Phoenix
Quarkus (JDBC)
Quarkus (Reactive)
React
React Router
Reflex
Remix
SolidStart
Sveltekit
Symfony
Hono
RedwoodSDK
Vue
Languages
.NET
Elixir
Go
Java
JavaScript
Python
Rust
ORMs
Django (Django ORM)
Drizzle
Elixir Ecto
Kysely
Knex
Laravel (Eloquent)
Prisma
Ruby on Rails (ActiveRecord)
SQLAlchemy
Tortoise ORM
TypeORM
Better Drizzle
Migrate to Neon
Overview
Utilities
Import Data Assistant
pg_dump / pg_restore
pgcopydb
Migrate from
RDS
AlloyDB
Azure
Cloud SQL
Digital Ocean
Firebase
Heroku
MSSQL
SQLite
MySQL
PlanetScale
Railway
Render
Supabase
Turso
Neon to Neon
Schema-only
Logical replication
Postgres
Neon to Neon
Supabase
RDS
AlloyDB
Azure
Cloud SQL
Migration services
AWS DMS
Region migration
Overview
Azure regions deprecation
Neon to another region
Neon to Lakebase
Postgres-compatible export
CSV
Sample data
/
Tour the Neon Console
Tour the Neon Console
Sign up and explore Neon's core features — the SQL Editor, branching, the Tables view, and Managed Better Auth
Copy page
What you will learn:
How to view and modify data in the console
Create an isolated database copy per developer
Reset your branch to production when ready to start new work
Related topics
About branching
Branching workflows
Connect Neon to your stack
Managed Better Auth
This tutorial walks you through your first steps using Neon as your Postgres database. You'll explore the Neon object hierarchy and learn how database branching can simplify your development workflow.
About branching
Each
branch
is a fully-isolated copy of its parent. We suggest creating a long-term branch for each developer on your team to maintain consistent connection strings. You can reset your development branch to production whenever needed.
After signing up, you'll start with a
production
branch:
production
is your project's root default branch (default: 0.25-2 CU, adjustable up to 56 CU)
You can create additional branches for development, staging, and other environments. For development branches, consider using a smaller compute size (0.25-1 CU) to optimize costs, while keeping production appropriately sized for your workload. All computes scale to zero after 5 minutes of inactivity by default, which keeps costs low for development branches. On paid plans, you can disable this for production if you need always-active compute. See
Scale to zero
.
Sign up
If you're already signed up, you can skip ahead to
Step 2
.
If you haven't signed up yet, you can sign up for free here:
https://console.neon.tech/signup
Sign up with your email, GitHub, Google, or other partner account.
For information about what's included with the Free and paid plans, see
Neon plans
.
Onboarding in the Neon Console
After you sign up, you are guided through some onboarding steps that ask you to create a
Project
.
The steps should be self-explanatory, but it's important to understand a few key points:
In Neon, everything starts with the
Project
It is the top-level container that holds your branches, databases, and roles. Typically, you should create a project for each repository in your application. This allows you to manage your database branches just like you manage your code branches: a branch for production, staging, development, new features, previews, and so forth.
We create a production branch for you
production
is the root default branch. It hosts your database, role, and a compute that you can connect your application to
You can create additional branches for development, staging, previews, and other workflows as needed
At this point, if you want to just get started connecting Neon to your toolchain, go to
Connecting Neon to your tools
. Or if you want a more detailed walkthrough of some of our key console and branching features, let's keep going.
Working with a team?
Your organization is now set up. You can start inviting teammates immediately. See
Invite members
.
Add sample data
Let's get familiar with the
SQL Editor
, where you can run queries against your databases directly from the Neon Console, as well as access more advanced features like
Time Travel
and
Explain and Analyze
.
From the Neon Console, use the sidebar navigation to open the
SQL Editor
page. Notice that your default branch
production
is already selected, along with the database created during onboarding,
neondb
.
The first time you open the SQL Editor for a new project, the editor includes placeholder SQL commands to create and populate a new sample table called
playing_with_neon
.
For this tutorial, go ahead and create this sample table: click
Run
.
Every query you run in the SQL Editor is automatically saved with an AI-generated description, making it easy to find and reference your work later. For example, the sample table creation above will be saved with a description like "create and populate sample table in Neon". You can view your query history anytime by clicking the
History
button in the SQL Editor.
Or if you want to add the table from the command line and you already have
psql
installed:
CREATE
TABLE
IF
NOT
EXISTS
playing_with_neon(id
SERIAL
PRIMARY KEY
,
name
TEXT
NOT NULL
,
value
REAL
);
INSERT INTO
playing_with_neon(
name
,
value
)
SELECT
LEFT
(md5(i::
TEXT
),
10
), random()
FROM
generate_series
(
1
,
10
) s(i);
Your default branch
production
now has a table with some data.
Try the AI Assistant
Now that you have some sample data, let's explore how the AI Assistant can help you write SQL queries using natural language prompts.
From the SQL Editor, click the
AI Assistant
button in the top-right corner and try a few prompts:
Add three more rows to the playing_with_neon table with tech company names
Show me the highest value in the table
Calculate the average value grouped by the first letter of the name
Each query you run is automatically saved with an AI-generated description, making it easy to find and reuse queries later. For example, when you ask the AI Assistant to add company data, you should see a response like:
-- Text to SQL original prompt:
-- Add three more rows to the playing_with_neon table with tech company names
INSERT INTO
public.playing_with_neon (
name
,
value
)
VALUES
(
'Google'
,
1000
.
5
),
(
'Apple'
,
1200
.
75
),
(
'Microsoft'
,
950
.
25
);
With the description: "Add tech companies to playing_with_neon table"
Learn more about AI features in the
SQL Editor documentation
.
View and modify data in the console
Now that you have some data to play with, let's take a look at it on the
Tables
page in the Neon Console. The
Tables
page, powered by
Drizzle Studio
, provides a visual interface for exploring and modifying data and schemas directly from the console. The integration with Drizzle Studio provides the ability to add, update, and delete records, filter data, export data in
.json
and
.csv
formats, manage schemas (including creating and altering tables, views, and enums), create Postgres roles, and define RLS policies.
For a detailed guide on how to interact with your data using the
Tables
page, visit
Managing your data with interactive tables
.
Set up Managed Better Auth
Neon includes
managed authentication
, so your app's users live in your Postgres database and branch with the rest of your data.
From the Neon Console sidebar, open the
Auth
page and toggle Managed Better Auth on for your project. You'll get:
A sign-up / sign-in flow ready to wire up to any framework
Users and sessions stored in your own Postgres database — query the
neon_auth.users_sync
table directly alongside your application data
Branch-aware auth: every preview or development branch you create gets its own isolated copy of users and sessions
OAuth providers, email and password, magic links, and more, all configurable from the console
For framework-specific setup, see the
Managed Better Auth quickstarts
(Next.js, React, TanStack Router) or open the
Auth
tab in the console and follow the prompts.
Working with your development branch
Let's create a
development
branch and learn how to use the Neon CLI to manage branches and make schema changes in your development environment.
Create a development branch
From the Neon Console, navigate to the
Branches
page and click
Create branch
. Name it
development
, select
production
as the parent branch, and click
Create new branch
. This creates an isolated copy of your production data that you can safely modify.
Install CLI with Brew or NPM
Depending on your system, you can install the Neon CLI using either Homebrew (for macOS) or NPM (for other platforms).
For macOS using Homebrew:
brew
install
neonctl
Using NPM (applicable for all platforms that support Node.js):
npm
install
-g
neon
Authenticate with Neon
The
neon auth
command launches a browser window where you can authorize the Neon CLI to access your Neon account.
neon
auth
View your branches
First, list your projects to get your project ID:
neon
projects
list
You'll be prompted to select your organization. The output shows your project IDs:
Projects
┌─────────────────────┬────────────┬───────────────┬──────────────────────┐
│
Id
│
Name
│
Region
Id
│
Created
At
│
├─────────────────────┼────────────┼───────────────┼──────────────────────┤
│
cool-forest-12345678│
myproject
│
aws-us-east-2
│
2025-10-14T14:33:43Z
│
└─────────────────────┴────────────┴───────────────┴──────────────────────┘
Now list your branches using your project ID:
neon
branches
list
--project-id
cool-forest-12345678
┌──────────────┬────────────────────────────┬───────────────┬──────────────────────┐
│
Name
│
Id
│
Current
State
│
Created
At
│
├──────────────┼────────────────────────────┼───────────────┼──────────────────────┤
│
development
│
br-calm-sky-a5xd78mn
│
ready
│
2025-12-23T21:05:05Z
│
├──────────────┼────────────────────────────┼───────────────┼──────────────────────┤
│
✱
production
│
br-bold-wind-a4p92kpx
│
ready
│
2025-12-23T21:04:57Z
│
└──────────────┴────────────────────────────┴───────────────┴──────────────────────┘
This command shows your existing branches, including the
production
branch and the
development
branch you just created.
tip
To avoid specifying
--project-id
with each command, use
neon set-context
to set your default project and organization. See
set-context
for details.
Make some sample schema changes
First, let's make sure our development branch is in sync with
production
. This ensures we're starting from the same baseline:
neon
branches
reset
development
--parent
--project-id
cool-forest-12345678
Now that our
development
branch matches
production
, we can make some changes. The
playing_with_neon
table from
production
is now available in your
development
branch, and we'll modify its schema and add new data to demonstrate how branches can diverge.
You can use the
Neon SQL Editor
for this, but let's demonstrate how to connect and modify your database from the terminal using
psql
. If you don't have
psql
installed already, follow these steps to get set up:
Mac
Linux
Windows
brew
install
libpq
echo
'export PATH="/opt/homebrew/opt/libpq/bin:$PATH"'
>>
~/.zshrc
source
~/.zshrc
With
psql
available, let's work from the terminal to connect to your
development
branch's database and make changes.
Connect to your database
Get the connection string to your branch and connect to it directly via
psql
:
neon
connection-string
development
--database-name
neondb
--project-id
cool-forest-12345678
--psql
This command establishes the psql terminal connection to the
neondb
database on your development branch.
Modify the schema
Add a new column
description
and index it:
ALTER
TABLE
playing_with_neon
ADD
COLUMN
description
TEXT
;
CREATE
INDEX
idx_playing_with_neon_description
ON
playing_with_neon (
description
);
Insert new data
Add new data that will be exclusive to the dev branch.
INSERT INTO
playing_with_neon (
name
,
description
)
VALUES
(
'Your dev branch'
,
'Exploring schema changes in the dev branch'
);
Verify the schema changes
Query the table to verify your schema changes:
SELECT
*
FROM
playing_with_neon;
Your response should include the new description column and a new row where name =
Your dev branch
and description =
Exploring schema changes in the dev branch
:
id |
name
|
value
|
description
----+--------------------+-------------+--------------------------------------------
1
| c4ca4238a0 |
0
.
5315024
|
2
| c81e728d9d |
0
.
17189825
|
3
| eccbc87e4b |
0
.
21428405
|
4
| a87ff679a2 |
0
.
9721639
|
5
| e4da3b7fbb |
0
.
8649301
|
6
| 1679091c5a |
0
.
48413596
|
7
| 8f14e45fce |
0
.
82630277
|
8
| c9f0f895fb |
0
.
99945337
|
9
| 45c48cce2e |
0
.
054623786
|
10
| d3d9446802 |
0
.
36634886
|
11
| Your dev branch | | Exploring
schema
changes
in
the dev branch
(
11
rows
)
Check your changes with Schema Diff
After making the schema changes to your development branch, you can use the
Schema Diff
feature to compare your branch against its parent branch. Schema Diff is a GitHub-style code-comparison tool used to visualize differences between different branch's databases.
For this tutorial, Schema Diff helps with validating isolation: it confirms that schema changes made in your isolated development branch remain separate from the production branch.
From the
Branches
page in the Neon Console:
Open the detailed view for your
development
branch and click
Open schema diff
.
Verify the right branches are selected and click
Compare
. You can see the schema changes we added to our development branch highlighted in green.
Schema Migrations
A more typical scenario for Schema Diff is when preparing for schema migrations. While Neon does not provide built-in schema migration tools, you can use ORMs like
Drizzle
or
Prisma
to handle schema migrations efficiently. Read more about using Neon in your development workflow in
Connect Neon to your stack
.
Reset your development branch to production
After experimenting with changes in your development branch, let's now reset the branch to
production
, its parent branch.
Branch reset
functions much like a
git reset –hard parent
in traditional Git workflows.
Resetting your development branches to the
production
branch ensures that all changes are discarded, and your branch reflects the latest stable state of
production
. This is key to maintaining a clean slate for new development tasks and is one of the core advantages of Neon's branching capabilities.
You can reset to parent from the
Branches
page of the Neon Console, but here we'll use the Neon CLI.
Use the following command to reset your
development
branch to the state of the
production
branch:
Example:
neon
branches
reset
development
--parent
--project-id
cool-forest-12345678
If you go back to your
Schema Diff
and compare branches again, you'll see they are now identical:
When to reset your branch
Depending on your development workflow, you can use branch reset:
After a feature is completed and merged
Once your changes are merged into
production
, reset the development branch to start on the next feature.
When you need to abandon changes
If a project direction changes or if experimental changes are no longer needed, resetting the branch quickly reverts to a known good state.
As part of your CI/CD automation
With the Neon CLI, you can include branch reset as an enforced part of your CI/CD automation, automatically resetting a branch when a feature is closed or started.
Make sure that your development team is always working from the latest schema and data by including branch reset in your workflow. To read more about using branching in your workflows, see
Branching workflows
.
Additional branching features
Working with sensitive data?
Neon supports
schema-only branching
to create branches with just the database structure, without copying production data.
Need automatic cleanup?
Set branches to automatically
expire and be deleted
after a specified time period, perfect for temporary test branches or time-limited preview environments.
What's next
Building an app with users?
Set up Managed Better Auth
for managed sign-up, sessions, and OAuth. Identity lives in Postgres and branches with your data, so you can test full login flows on preview branches without touching production.
Need help?
Join our
Discord Server
to ask questions or see what others are doing with Neon. For paid plan support options, see
Support
.
Was this page helpful?
Yes
No
Thank you for your feedback!
Edit on GitHub
Previous
Tour the Neon backend
Next
Frameworks
On this page
About branching
1
Sign up
2
Onboarding in the Neon Console
3
Add sample data
4
Try the AI Assistant
5
View and modify data in the console
6
Set up Managed Better Auth
7
Working with your development branch
8
Make some sample schema changes
9
Check your changes with Schema Diff
10
Reset your development branch to production
What's next
Need help?
Set up Neon with AI
Copy neon init command
Neon Docs
Neon
Neon is part of the Databricks Platform
Neon status loading...
© Neon 2026. All rights reserved. Apache, Apache Spark, Spark, the Spark Logo, Apache Iceberg, Iceberg, and the Apache Iceberg logo are trademarks of the
Apache Software Foundation
.
Privacy Notice
Terms of Use
Neon Platform Terms
Modern Slavery Statement
California Privacy
Company
About
Blog
Careers
Contact Sales
Security
Resources
Docs
Changelog
Support
Community Guides
FAQs
PostgreSQL Tutorial
Startups
Community
Discord
GitHub
X.com
LinkedIn
YouTube
Compliance
CCPA
Compliant
GDPR
Compliant
ISO 27001
Certified
ISO 27701
Certified
SOC 2
Certified
HIPAA
Compliant
Compliance Guide
Neon’s Sub Contractors
Trust Center
