# Environments

## What is an environment?

In Servoy Cloud, an environment is a dedicated space where your application runs. Each environment has its own resources, configuration, and data — so what happens in development stays separate from production.

## Environment types

Servoy Cloud offers the following environment types:

### 1. Development (DEV)

The development (DEV) environment is where software developers write, test, and debug code. It allows the deployment of applications in the development phase without affecting other system components.

### 2. User Acceptance Testing (UAT)

The User Acceptance Testing (UAT) environment replicates the production setup, providing a platform for end-users to test the software and ensure it meets their requirements before deployment. This phase involves stakeholders verifying functionality, usability, and compatibility.

### 3. Pre-Production (PRE-PROD)

Also known as staging or pre-staging, the Pre-Production (PRE-PROD) environment closely mirrors the production setup. It serves as a final checkpoint before deploying changes to the live/production environment. Testing here ensures a seamless deployment and identifies potential issues that may arise in the live environment.

### 4. Production (PROD)

The PROD environment is the live environment where the software is accessible to end-users. It hosts the final, released version of the software. Changes are implemented cautiously and after thorough testing in previous environments to minimize disruptions to users.

### 5. Satellite (formerly "Remote / On-Premise")

A Satellite environment is a customer-hosted deployment where the Servoy Cloud Docker image runs on your own infrastructure rather than in the cloud. Satellite environments have nearly the same capabilities as cloud-managed environments — the main difference is that you manage the infrastructure yourself.

{% hint style="info" %}
The name "Satellite" replaced "Remote (On-Premise)" in the 2026.03 release. This is a label-only change — no configuration or behavior changed.
{% endhint %}

For setup instructions, see [Satellite (On-Premise) Deployment](https://github.com/Servoy/gitbook/blob/master/on-premise-deployment.md).

### 6. Local

Local environments are locally hosted Servoy installations that appear automatically in your dashboard — no manual setup needed.

Each local environment shows:

* **Status** — Online or Offline
* **Servoy version**
* **License key** in use (censored for safety)

When you open a local environment, you get a preview of the Servoy Cloud features that would become available if you migrate.

## Metrics and information

Each clickable card provides actionable insights and key metrics regarding the environment. These include:

* **Environment name**
* [**Latest Build Package Information**](/reference/servoy-cloud/cloud-control-center/application-overview/applications/pipelines/jobs/packages.md#package-details): Includes build date, build status, and build number.
* [**Real time status**](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/system-health.md): Online or Offline
* [**Real time system health**](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/system-health.md): Healthy, At-Risk, or Critical
* [**Real time users**](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/users.md)**:** real time user count **in** the environment
* [**Type of environment**](#environment-types): Development, UAT, Pre-prod, Production

{% hint style="info" %}
Metrics present on environment cards are clickable and navigate to a [detailed view](#detail-view) of the corresponding metric within the environment details
{% endhint %}

## Detail view

### File manager

The File Manager is accessible through the environment's menu by selecting **Manage Files**. This tool provides a structured view of directories and files, allowing users to manage their environment's file system efficiently.

1. Navigate to Application details
2. Access Environments (if available)
3. Locate the context menu on the environment card
4. Click on "Manage files"

**Features:**

1. **Folder Structure Navigation:**
   * Browse directories, including nested folders, for a clear hierarchy view.
   * Displays file sizes and last modified dates for better organization.
2. **Right-Click Context Menu:**
   * **New Folder:** Create a new folder in the selected directory.
   * **Upload:** Add files directly to the selected location.
   * **Download:** Retrieve files from the environment to your local machine.
   * **Delete:** Remove selected files or folders permanently.

{% hint style="info" %}
**Usage Tips:**

* Use the folder tree on the left to navigate quickly.
* Right-click on files or folders to access the context menu for management actions.
* Check file sizes and modification dates to identify the latest updates.
  {% endhint %}

### Launch Environment

To launch a specific Servoy Cloud environment in the browser, follow these steps:

1. Navigate to Application details
2. Access Environments (if available)
3. Locate the context menu on the environment card
4. Click on "Launch Environment"

### Delete Environment

Servoy Cloud environments can be permanently deleted, but this action should be considered carefully.

To delete an environment, follow these steps:

1. Go to Application details
2. Access Environments (if available)
3. Find the context menu on the environment card
4. Select "Delete Environment"


---

# Agent Instructions: 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:

```
GET https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.