Skip to main content
Legia

Apps & Software

What is Staging?

Also called staging server, staging environment, test server.

Short definition

Staging is a test environment built to resemble the production system as closely as possible, where changes to an application or website are checked and approved before release to real users.

How it works

There are usually three environments: development, where developers work; staging, where changes are tested; and production, which users rely on. New changes are first deployed to staging with the same configuration, software versions, and data structure as production. The QA team and users from the company review them there, including processes that are hard to try in production, such as data migration or database structure changes. Once approved, the exact same changes are released to production, ideally through an automated CI/CD pipeline.

Example in a company

The finance team asks for a change to the discount formula in the sales app. The change is deployed to staging, then finance staff try a dozen sample transactions and compare the results with manual calculations. One rounding error is found and fixed before it touches real transactions.

What to watch out for

A staging environment that differs too much from production gives a false sense of security. Data in staging should be sample data or masked data, not a raw copy of customer data, because staging is often less tightly secured. Integrations with third parties, such as a payment gateway or email delivery, are pointed to test mode so they do not trigger real transactions or messages. Access to staging is restricted, and its pages are marked so search engines do not index them and users do not confuse them with the real system.

Related Legia service DevOps & CI/CD Automated release pipelines, consistent environments, and monitoring that your own team can run.