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

# Sandbox environment

> An isolated environment that replicates your production configuration to test features, ingestion, transformations, and alerts before publishing them

<Info>
  **Available on the Corporate plan.** This feature is part of woku's enterprise capabilities. [Talk to our sales team](https://woku.app/pricing).
</Info>

woku includes a **sandbox environment**: an isolated space where you can test
features and configurations **before taking them to production**. The
sandbox **replicates the production configuration**, so what you validate
there behaves the same when you promote it, but without touching your data or
your real customers.

<Note>
  The sandbox environment is available on the **Corporate** plan. Each company
  has its own sandbox, isolated from its production environment.
</Note>

## What the sandbox isolates

The sandbox is a parallel environment that **does not share state** with production.
The following remain separate:

| Resource                       | Production                     | Sandbox                                  |
| ------------------------------ | ------------------------------ | ---------------------------------------- |
| **Data** (wokus, reviews, NPS) | Real customer data             | Test data, disposable                    |
| **Surveys and tools**          | The ones your customers see    | Copies for experimenting                 |
| **Integrations**               | Connected to your real systems | Point to test endpoints                  |
| **API keys**                   | Production key                 | Independent sandbox key                  |
| **Ingestion pipelines**        | Live                           | Isolated, without affecting real reports |

Nothing you do in the sandbox affects production reports, alerts, or data.
You can delete and recreate test data with complete freedom.

## Switching environments

Each environment has its **own key**. To point your integration at the
sandbox, just use the sandbox key instead of the production one; the base
URL is the same.

<Steps>
  <Step title="Get the sandbox key">
    In the admin application, go to **Company → Information** and open the
    **Sandbox** tab to copy the **Sandbox Key**. It is
    independent from your production key.
  </Step>

  <Step title="Configure your integration">
    Use that key in the `Authorization` header of your calls. The company and
    its data are resolved by the key, so the same code works
    against sandbox or production just by changing the key.

    ```
    Authorization: Bearer <Sandbox-Company-Key>
    ```
  </Step>

  <Step title="Promote to production">
    When the configuration works as expected, replicate it in production by
    switching back to the production key. Since the sandbox mirrors the
    same configuration, there are no surprises when promoting.
  </Step>
</Steps>

<Tip>
  If you use the [React Native SDK](/docs/en/desarrollo/sdk-react-native), just
  initialize it with the sandbox `publicKey` to send all captures to the
  test environment.
</Tip>

## It mirrors the production configuration

The sandbox **mirrors the production configuration**: same folder
structures, same ingestion schemas, same tracker, survey, and rule
definitions. This lets you reproduce a real scenario and trust that what you
validate will behave the same when you promote it.

You can sync the production configuration into the sandbox whenever you
want to start from a clean and representative state.

## Safe for testing ingestion, transformations, and alerts

The sandbox is designed to exercise the full pipeline without risk:

* **Ingestion**, Send payloads by event or in batch against the sandbox
  key and verify that they are normalized and validated as you expect. See the
  [ingestion and extraction limits](/docs/en/desarrollo/API#ingestion-and-extraction-limits).
* **Transformations**, Test your
  [code transformation](/docs/en/desarrollo/transformaciones) functions on sample
  data and review the output before activating them in production.
* **Alerts**, Trigger test conditions to confirm that alerts
  fire and are delivered correctly, without notifying your real
  teams.

<Warning>
  Sandbox data is test data and can be purged. Do not use the sandbox
  as a backup or store information there that you need to keep.
</Warning>