Guide · updated
Running AEM after go-live: what a managed ops retainer should cover
Adobe runs the AEM as a Cloud Service platform and updates it continuously. Your code, configuration, content model and integrations are still yours to run. A managed ops retainer covers that part. Use this list to compare offers, including ours.
What should be in scope
| Area | What good looks like |
|---|---|
| Releases | Regular releases through Cloud Manager pipelines, with code review, a rollback plan and release notes for authors. |
| Adobe deprecations | Someone watches Adobe's deprecated-features page and Actions Center emails, and fixes affected code before enforcement dates. |
| Monitoring | Pipeline health, error rates, CDN cache hit ratio and integration failures, with agreed alert thresholds. |
| Incidents | Response times by severity, an on-call path, and coordination with Adobe support when the platform is involved. |
| Small changes | A monthly allowance of hours for component tweaks and content model changes, with unused-hours rules stated. |
| Security | Dependency updates, secrets in Cloud Manager environment variables, and access reviews for Cloud Manager and AEM groups. |
| Reporting | A monthly report: releases, incidents, deprecation status, hours used. |
What to check in the contract
- Which response times are commitments and which are targets.
- Who holds Cloud Manager roles, and how access is removed when people leave.
- How work beyond the allowance is quoted.
- Exit terms: documentation and access handed back when the retainer ends.
Our Managed AEM Ops and Deprecation Watch services are described on the services pages, with published starting prices. Read the scope there, and ask us anything that is not covered.