---
title: Create a Neon Twin
subtitle: Learn how to Twin your production database with Neon
summary: >-
  Covers the creation of a Neon Twin, a clone of your production database,
  enabling developers to work in isolated environments with automatic
  synchronization and efficient management for development and testing
  workflows.
enableTableOfContents: true
isDraft: false
updatedOn: '2026-02-06T22:07:33.025Z'
---

<CTA title="Explore our dev/test use case" description="Move development and testing to Neon—keep production right where it is.<br/><br/>Read more about our dev/test use case <a href='/use-cases/dev-test'>here</a>." isIntro></CTA>

## What is a Neon Twin?

A Neon Twin is a full or partial clone of your production or staging database, providing developers and teams with isolated, sandboxed environments that closely mirror production.

![Dev/Test Twin Workflow](/use-cases/dev-test-twin-workflow.png)

## Designed for efficiency

Creating a Neon Twin will streamline development workflows, enhance productivity, and help teams ship faster—all while being more [cost-effective](/docs/introduction/pricing-estimation-guide) and easier to manage than traditional development/testing environments.

## Automatically synced

The workflows in this section enable automatic synchronization between your production database and your Neon Twin.

## Instant Branches

With a Neon Twin created, [branches](/docs/introduction/branching) can be quickly spun up or torn down, enabling developers to build new features or debug issues—all within their own isolated environments with a dedicated compute resource.

Branches can be created and managed through the [Neon console](https://console.neon.tech/) or programmatically via the [API](/docs/reference/api-reference).
