> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data planes

Data planes run your apps' backend code and connect to your data sources. They're part of every Superblocks instance, in both [deployment models](https://docs.superblocks.com/enterprise/deployment-overview.md). See [Platform architecture](https://docs.superblocks.com/enterprise/architecture/platform-architecture.md#data-planes) for what runs in a data plane.

```mermaid theme={null}
flowchart LR
  subgraph I["Your Superblocks instance"]
    CP["Control plane"]
    subgraph R1["Primary region"]
      NP["Non-production data plane"]
      PP["Production data plane"]
    end
    subgraph R2["Another region (optional)"]
      PR["Production data plane"]
    end
    CP --> NP
    CP --> PP
    CP --> PR
  end
  subgraph Y["Your data sources"]
    ND["Non-production databases and APIs"]
    PD["Production databases and APIs"]
    RD["Data in the other region"]
  end
  NP -- "IP allowlist or private networking" --> ND
  PP -- "IP allowlist or private networking" --> PD
  PR -- "IP allowlist or private networking" --> RD
```

Each data plane connects to the data sources for its environment and region. The control plane manages your apps, but your apps' backend code reaches your data sources only from a data plane. To keep production data out of development, link production credentials only to production. See [Manage environments and data tags](https://docs.superblocks.com/admin/environments.md).

## Environments

Each instance has separate data planes for non-production and production:

* **Non-production:** Runs backend code while your team builds and tests apps.
* **Production:** Runs backend code for deployed apps.

You can add data planes for more environments. For example, you can run separate development, staging, and production data planes. Contact your Superblocks team to add a data plane.

## Regions

Your instance has a primary region, and its data planes run there by default. To keep backend code close to data in other places, you can add data planes in other regions. See [Supported regions](https://docs.superblocks.com/enterprise/architecture/supported-regions.md#data-plane-regions).

## Where data planes run

| | Dedicated Cloud | Managed BYOC |
| - | - | - |
| Location | Superblocks-managed AWS | Your AWS account |
| Network | Managed by Superblocks | One VPC for each data plane, built by Managed BYOC or [one you own](https://docs.superblocks.com/enterprise/cloud-prem/configure/existing-vpc.md) |

## Connect to your data

Data planes reach your data sources over the internet or over private networking, depending on your deployment model.

| | Dedicated Cloud | Managed BYOC |
| - | - | - |
| IP allowlisting | Allowlist your data plane's egress IP addresses | Allowlist your [egress IP addresses](https://docs.superblocks.com/enterprise/cloud-prem/configure/existing-vpc.md#egress-ip-addresses) |
| Private networking | Coming soon. Works across clouds, including AWS, Google Cloud, and Azure | VPC peering, Transit Gateway, or PrivateLink to data sources in your other AWS accounts |
| AWS VPC endpoints | | Supported, local to your deployment |

For how to configure a data source to accept connections, see [Database connections](https://docs.superblocks.com/integrations/auth/database-connections/index.md#networking).

## Related pages

* [Platform architecture](https://docs.superblocks.com/enterprise/architecture/platform-architecture.md)
* [Supported regions](https://docs.superblocks.com/enterprise/architecture/supported-regions.md)
* [Use your own VPC](https://docs.superblocks.com/enterprise/cloud-prem/configure/existing-vpc.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.