> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/technical-guides/how-to-guides/admin-setup-and-configuration/how-to-manage-the-dev-and-live-environments-with-batch.md).

# How to manage the dev and live environments with Batch?

Here are the best practices to manage both environments.

## How to manage the dev and live environments with Batch?

A staging environment refers to a parallel server environment for testing websites and software applications in conditions as close as possible to the live environment, without compromising the organization's current data or interrupting its operations.

You should always integrate Batch in a development environment and then go into production mode after everything has been tested and validated.

For this matter, we strongly recommend:

{% stepper %}
{% step %}
Creating **two applications per OS** (Android, iOS, Web) on the dashboard: one for tests and one for production (e.g. *MyApp* and *\[DEV] MyApp*).
{% endstep %}

{% step %}
These apps will then be grouped into **two Omnichannel projects**.
{% endstep %}
{% endstepper %}

For instance:

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2FOnWV8i5ojTdvaTjdadTQ%2Ftechnical-guides_dev-live-env_02052025.png?alt=media&#x26;token=3b9efe5c-9054-44d9-b737-e5ed994ece61" alt="Screenshot of the Batch dashboard showing two omnichannel projects in a dropdown menu (&#x22;The Store&#x22; and &#x22;[DEV] The Store&#x22;)"><figcaption></figcaption></figure>

{% hint style="info" %}
Thereafter, DEV projects can only be displayed to developers so as not to disturb your operational teams on the dashboard (refer to the [Project-level Permissions documentation](/getting-started/features/customer-engagement-platform/settings/manage-team.md#project-level-permissions) for more details).
{% endhint %}

{% hint style="warning" %}
**Avoid using the Dev API key on production projects.** The Dev API key (its value starts with `DEV`) is meant for development and testing only. Using it in production has several drawbacks:

* **Your stats will be inaccurate.** Batch does not compute analytics for the Dev API key, so any campaign or traffic sent with it is ignored in your KPIs (delivery, open and click rates, etc.).
* **Deliverability can suffer.** Dev traffic is not treated as production traffic and can be rate-limited by push providers such as FCM or APNs, which may throttle or drop your notifications.
* **It pollutes your production data.** Mixing Dev installs and tokens into a production app makes your audiences and targeting unreliable.

Always ship your production app with the Live API key, and reserve the Dev API key for a dedicated development app or project.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/developer/technical-guides/how-to-guides/admin-setup-and-configuration/how-to-manage-the-dev-and-live-environments-with-batch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.