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

# Environments

> Organize your integrations & data with environments

Environments help you segment your integration configuration and customer data across different stages of your development lifecycle.

## Overview

Each environment in your Nango account is completely isolated with its own:

* Integration configurations
* [Functions](/guides/functions/functions-guide)
* [Connections](/guides/auth/auth-guide)
* Environment-specific settings

<Info>
  Each Nango account comes with **dev** and **prod** environments by default. Additional environments are available depending on your [pricing plan](https://www.nango.dev/pricing).
</Info>

## Production environments

Any environment can be designated as a production environment. This affects how team members interact with it based on their [role](/guides/platform/security#team-and-roles).

**To mark an environment as production:**

1. Open the environment settings (gear icon in the top navigation)
2. Toggle the **Production environment** switch

<Info>
  Only **Full Access** team members can toggle the production flag. Once an environment is marked as production, **Support** members get read-only access to it, and **Contributor** members lose access entirely.
</Info>

By default, the `prod` environment created with your account is already marked as production.

## Best practices

**Mirror your application environments**

We recommend creating Nango environments that match your application's deployment stages. For example:

* Local development → dev environment
* Staging → staging environment
* Production → prod environment
* Demo → demo environment

**Deploy to specific environments**

When you deploy [Functions](/guides/functions/functions-guide), you always target a specific environment. This ensures changes are tested before reaching production.

## Related guides

* [API keys](/reference/backend/http-api/api-keys) - scope keys per environment.
* [CI/CD](/guides/functions/ci-cd) - deploy functions safely across environments.
* [Self-host Nango](/guides/platform/self-hosting) - plan environments for self-hosted deployments.