Skip to content

Setting up a staging environment

A staging environment is a copy of production where changes are checked before release. Only the approved version goes live.

Background

Changes made directly on the live website are risky. A faulty update or new feature can break forms, checkout or log-in, and customers may notice before your team does.

Requirements for staging

  • the same versions and configuration as production, aligned regularly

  • password protection and exclusion from search engines

  • emails intercepted, never sent to real recipients

  • deployment via the same pipeline as production

Data protection for test data

Real customer data does not belong unprotected on a test system. Sample data or anonymised copies keep tests realistic without spreading personal data.

Acceptance and approval

On staging, your team reviews new content, features and updates at its own pace and approves them. The approved version then goes live automatically, without manual steps.

Approach

Staging runs on the same or comparable infrastructure. We agree access, test data and the approval process with you.

Project enquiry

Back to top