---
title: "Deploy a Configuration to a Production Environment"
slug: "deploy-a-configuration-to-an-environment"
description: "Describes how to deploy a revision of a Lasernet configuration to a production Lasernet Core environment."
tags: ["Configuration", "Deploy", "Lasernet Core 11"]
updated: 2026-05-26T14:53:44Z
published: 2026-05-26T14:53:44Z
canonical: "kb.lasernetgroup.com/deploy-a-configuration-to-an-environment"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy a Configuration to a Production Environment

**Applies to:** Lasernet Core 11

After you have tested your changes and verified that the configuration works, the next stage of the process is to send the configuration to a production Lasernet Core environment.

First, [you must “commit” the configuration changes](/v1/docs/commit-configuration-changes-to-the-repository), which will create a new revision of the configuration. Then, at an appropriate time, you can use Deploy Commit to deploy that new revision to a production environment.

> [!NOTE]
> Note
> 
> To “deploy” a configuration means to send it to a Lasernet Core environment, which will run the configuration.

> [!NOTE]
> Note
> 
> For Lasernet Core 10 documentation on this subject, see the [Lasernet Config Server and Deployment Guide](/v1/docs/lasernet-config-server-and-deployment-guide).

## Deploy Commit

You can use Manage (or the Lasernet Config web app) to deploy any revision of a configuration.

You can use Lasernet Developer to deploy only the latest revision of a configuration.

### Manage

To deploy a revision of a configuration to one or more environments, follow these steps:

1. In the upper-right corner, click **Deploy** (1).

![A number annotated screenshot that indicates elements of the Deploy Configuration window.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/deploy configuration in manage.png)
2. In the **Deploy Configuration** window:
  1. Use the **Environments** list (2) to select which environments you want to deploy the configuration to. You can select more than one environment.
  2. Select a configuration from the **Configuration** list (3).
  3. In the revision list, select which configuration revision you want to deploy (4).
3. Click **Confirm** (5).

After the process completes, the selected environments are running the configuration.

### Lasernet Config Web App

> [!NOTE]
> Note
> 
> The Lasernet Config web app was provided with earlier versions of Lasernet Core. It is a legacy web app and will be deprecated in a future version of Lasernet Core.

**Expand for information**

To deploy a revision of a configuration to one or more environments, follow these steps:

1. In the toolbar, click **Deploy** (see 1 in the image below).
2. In the **Deploy Configuration** window, select the checkbox for each environment that you want to deploy the configuration to (2). You can select more than one checkbox.
3. Select the configuration from the list (3).
4. In the revision list, select which configuration revision you want to deploy (4).
5. Click **OK**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/deploy configuration.png)

### Lasernet Developer

To deploy the latest revision of a configuration to one or more environments, follow these steps:

1. In Lasernet Developer, [open the configuration](/v1/docs/create-or-import-a-configuration) that you want to deploy.
2. In the Lasernet Developer toolbar, click **Deploy Commit** (see 1 in the image below).

![A number annotated screenshot that supports instructions on how to deploy a revision to a Lasernet environment](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/deploy commit.png)
3. In the **Deploy configuration** window, select the checkbox (2) for each environment that you want to commit the latest revision to.

> [!NOTE]
> Note
> 
> You can only deploy committed objects. If the workspace currently contains any uncommitted objects or resources, Lasernet Developer will display a warning.
> 
> ![A screenshot of a warning in the Deploy Configuration window that uncommitted objects or resources exist in the loaded configuration](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/uncommitted objects.png)
> 
> To commit objects and resources before deploying the configuration, click **Commit** below the warning then [commit the objects and resources](/v1/docs/commit-configuration-changes-to-the-repository).
> 
> To deploy without committing the objects and resources, do not commit the changes and proceed with the following steps.
4. Click **Ok**. Lasernet Developer displays a progress bar for the deployment.
5. After Lasernet Config Server has deployed the configuration, click **Close**.

After the process is complete, the selected environments are running the configuration.