---
title: "Non-Production Environments"
description: "Lucanet offers non-production environments for customers with an existing production license. These environments are isolated copies of your production system and allow you to test safely without affecting your live data or configuration.\nTwo types of non-production environments are available for limited solutions:\nTest Update Environment and  Sandbox Environment."
source_url: https://support.lucanet.com/en/documentation/getting-started/non-production-environments
language: en
last_updated: 2026-05-28
---
# Non-Production Environments

## Overview

Lucanet offers non-production environments for testing without affecting your live data or configuration. These environments are isolated copies of your production system. Two types are available for limited solutions:

- **Test update environment**: runs the **next** planned software version

- **Sandbox environment**: runs the **same** software version as production

## Test Update Environment

The test update environment allows you to test an upcoming software release before it becomes available in the production system. Lucanet provides this environment ahead of a planned production update.

**This environment is particularly relevant if your business processes are subject to legal or compliance requirements**, where pre-release validation helps ensure continuity before the update takes effect.

At the end of the testing period, your production system is updated to the new software version.

## Sandbox Environment

The sandbox environment reflects your current production version. It can be used for testing configurations, training, or validating workflows before applying changes to production. Unlike the test update environment, it is not tied to a release cycle and remains available on an ongoing basis.

## Getting Access

Non-production environments can be purchased as an add-on to your existing license. For information on availability and pricing, please contact your account manager.

Once your environment is provisioned, the designated initial user receives an e-mail with the URL to the environment and login credentials. Note that each test environment is provided with its **own URL** and **separate credentials**, which differ from those used for the production system.

The initial user can activate other users, who then receive an e-mail invitation with their login details.