> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/environments/environments.md).

# Environments

What environments does emSigner provide?

emSigner provides multiple, logically isolated environments to support **customer usage, testing, internal validation, and live production operations**. This separation ensures secure execution, controlled change management, and reliable eSignature services.

***

#### External (Customer-Facing) Environments

**Production Environment**\
The Production environment is the **live customer-facing environment** used for executing **legally valid eSignature transactions**. It is designed for **high availability, security, and scalability**, supporting enterprise and high-volume signing workflows.

**Sandbox Environment (Customer)**\
The Sandbox environment is provided to customers for **integration testing, API experimentation, and workflow validation**. It allows customers to test envelope creation, signing flows, and integrations without impacting the Production environment.

***

#### Internal Environments

**Demo Environment (Internal)**\
The Demo environment is used by emSigner teams for **internal demonstrations, pre-sales engagements, and training**. It is intended to showcase product capabilities and is not meant for customer testing or live transactions.

**Development Environment (Internal)**\
The Development environment is used by emSigner engineering teams for **feature development, configuration changes, and initial integration work**. It is fully isolated from customer-accessible environments.

**QA Environment (Internal)**\
The QA environment is used for **quality assurance and validation**, including functional testing, integration testing, regression testing, and performance checks prior to release into Production.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.emsigner.com/environments/environments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.