Enterprise Deployment — overview
Purpose: Index of deployment pages and the principles every AEM release follows.
Who this page is for
| Audience | Why it matters to you |
|---|
| All engineers | Everyone ships |
| Platform engineers | Process owners |
Principles
- One immutable artefact per release, promoted unchanged through environments.
- The pipeline is the only write path to /apps and OSGi config — no console edits, no manual packages.
- Every deploy is verified the same way (bundles, health, smoke) — automation, not eyeballs.
- Rollback is planned before deploy, and it is a pipeline run, not archaeology.