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

# Environments

## Overview

Stigg supports the creation of multiple environments in each account in order to support your existing product development process, for example: Development, Staging, Production, etc.

Every environment is **isolated** from one another.

## Environment types

Stigg supports 2 environment types:

1. **Non-production** - an isolated sandbox that can be used for testing and iterating on pricing and packaging without affecting your real customers
2. **Production** - a live environment where your real customers interact with the final, stable version of your product

The following table summarizes the main difference between each environment type:

|                                                                                  | Non-production environment                                                                                                        | Production environment                                                                               |
| :------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------- |
| Purpose                                                                          | An isolated sandbox that can be used for testing and iterating on pricing and packaging **without** affecting your real customers | A live environment where your real customers interact with the final, stable version of your product |
| Stripe integration                                                               | Only to test Stripe accounts                                                                                                      | Only to production Stripe accounts                                                                   |
| Environment usage (number of products, number of subscriptions, reported events) | Excluded from your Stigg subscription                                                                                             | Enforced according to your Stigg subscription                                                        |
| SLA commitment                                                                   | No                                                                                                                                | Yes                                                                                                  |

<Note>
  By default, when a Stigg account is created it includes 2 environment - development (non-production) and a production environment
</Note>

## Creating a new environment

To create a new environment, navigate to the Settings > Environment section.

Click on **+ Add**.

Enter the following information:

1. Environment name
2. Color which will be used to distinguish different environments from one another
3. Description (optional)
4. Environment type - production, non-production

<Warning>
  After an environment is created, its environment type (non-production / production) can't be modified.
</Warning>

<Note>
  When a new environment is created, a default product for that environment will be automatically created.

  The product name will be the same name as the account name, for example: if your account name is **Acme**, an **Acme** product will automatically be created in every newly created environment.

  You can edit the name of the default product, or even remove it altogether and create a new one.
</Note>

## Enforcing client-side security

When your client-side (frontend) application is integrated with Stigg it uses the publishable key, which is publicly accessible to anyone.

While the Stigg platform limits access for that API key to a minimum, some sensitive data may still be accessible by a malicious actor (e.g. by guessing customer ID).

To ease the integration process, Stigg doesn't enforce client-side security in newly created environments.

It's highly recommended to prevent any un-authenticated access to data using the publishable key, by configuring Stigg to verify the identity of requests that originate from your client-side application.

For more details see:

<Card title="Hardening Client-Side Access" icon="shield-halved" href="/api-and-sdks/integration/frontend/hardening-client-side-access" />

## Editing environment details

To edit the details of an environment, click on the dotted menu of the relevant environment and select the **Edit** action.

Save the changes.

## Deleting environments

To delete the details of an environment, click on the dotted menu of the relevant environment and select the **Delete** action.

Enter the environment name in the confirmation dialog and click on **Delete**.

<Warning>
  Deleting an environment is an irreversible action that will cause the permanent removal of all of its data from Stigg.
</Warning>