# Staging environment

URL: https://tnb-tech.com/en/glossary/staging-environment/

## What is a staging environment?

A staging environment is a private copy of a website or online shop, hidden from customers and search engines, where changes are tried before they reach the live site. Updates, new features and redesigns run there first, and forms and checkout are tested. Only then is the change deployed. A mistake found on staging costs the team an hour, not the business its orders.

**Example**

A shop takes 40 orders a day at an average order value of €50: about €2,000 in daily revenue, or over €80 an hour. An update to its payment module comes out. Installed straight on the live site, it breaks the last step of checkout on a Saturday evening, and nobody notices until Monday. That is around 40 hours in which the shop cannot take an order, and more than €3,000 of revenue at risk. Installed on staging first, the same update fails on the very first test order, and the live site stays on the old version until the fix is ready.

**Why it matters for a business**

Websites rarely break on their own. They break when something changes: a platform or module update, a new PHP version. Staging turns those surprises into planned work, and it lets you see a redesign or a new feature before your customers do.

**What makes a staging environment useful**

- It sits behind a password, not just a noindex tag: the tag gets lost on a deployment, or never gets read at all when robots.txt blocks crawling, and the copy surfaces in Google as duplicate content.
- It runs the same platform, module and PHP versions as the live site; otherwise the test proves nothing.
- Payments run in the payment provider’s test mode, and outgoing emails never reach real customers.
- Its copy of the database holds customers’ personal data, so GDPR applies to it too: access only for the people testing, or anonymised data.

**How a change reaches the live site**

Deployment is a separate step, with a backup taken just before it. What moves is the code and the settings, not the whole database: while testing went on, the live shop kept taking orders and sign-ups that copying staging over the top would wipe out. After deployment, the same test order is placed on the live site.

**What to ask**

- Do you keep a staging environment for our site, and who can get into it?
- Does every update go through it first, or only the large changes?
- How do you deploy without losing the orders placed in the meantime?
- Is there a backup right before each deployment, and how quickly can the old version come back?Tested updates are part of our website maintenance: the platform, modules and certificates are updated on time and after a check, and the database and files are backed up every day.

- Services: [Website maintenance](https://tnb-tech.com/en/services/website-maintenance/)
- Glossary: https://tnb-tech.com/en/glossary/