# Your environments

You integrate against a **test environment** first and move to **production** later. They are separate: each has its own Engine URL, its own key and its own DevLab account.

## What changes between them

| What | Test environment | Production |
| --- | --- | --- |
| Engine URL | In your kit, in [Your integration](/integration). | In your kit for production, when Neurologyca gives it to you. |
| API key | One per team and environment, in [Your account](/account). | A different one: a test key does not open production. |
| DevLab account | Its own account and session. | Another account: a session in one environment does not open the other. |
| Measurement | Every standard organization has it. | Not yet. |
| Deferred processing | Record, upload and process with Neurologyca's processing service (Preview), turned on for your organization. | The same service, with your production access, when Neurologyca gives it to you. |
| `DELETE /users/{externalId}` | Physical and irreversible. | Physical and irreversible. |

This DevLab is connected to **production**.

## Moving to production

1. Integrating into an application, to use it with people, needs a commercial agreement with Neurologyca first ([Pricing](/docs/access/pricing/)). Then ask Neurologyca for your production access: a DevLab account, a key and your production kit.
2. Change `ENGINE_BASE` and `ENGINE_API_KEY` in your backend. The rest of what differs (for example the signed-URL secret, the webhook secret and the processor URL in deferred mode) are also your backend's environment values: see the [production checklist](/docs/guides/production-checklist/). Your code does not change.
3. Check them: `POST /token` with the new key answers `200`, and a harmless read such as `GET /catalog/contexts` lists your organization's contexts.
4. Create your people again: they do not move between environments. `DELETE /users/{externalId}` is physical and irreversible in both, so never point a cleanup script at production by mistake.
