# Environments

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.