Pre-prod
Both “preprod” and “pre-prod” are correct (in Russian, «препрод» and «предпрод»). It is an environment set up like production where a change gets its last check before release: the same settings and a fresh copy of production data. The word comes from pre-production. Some teams call it staging, others keep it as a separate step after the test environment.
How pre-prod differs from the test environment
| Test | Pre-prod | |
|---|---|---|
| What it checks | that everyone’s changes work together | how it behaves like on production |
| Settings | convenient for testing | same as production |
| Data | a copy of production or mocks | a fresh copy of production |
| Always there | almost always | not always |
Questions about pre-prod
- What is pre-prod? · The step right before production: a copy of the live environment where a change is checked under real conditions.
- Are pre-prod and staging the same? · In some teams yes, in others pre-prod comes after the test environment. Check how your team uses the words and agree on one.
- Do you need pre-prod? · Small teams usually get by with a test environment and production. Pre-prod lengthens the delivery cycle: quality goes up, but so does time to market, because a change takes longer to reach users. It is for places where a mistake in production is expensive.
- Where does pre-prod data come from? · From a dump: a copy of the live database data in one file. Personal data is removed from it.
- What does an AI agent do on pre-prod? · Runs checks. Changes reach it through a release; the agent does not edit it directly.
Source: Wikipedia: Deployment environment