AEM Managed Services: What Adobe Runs and What a Partner Runs

AEM managed services can mean two different things. Adobe runs the platform itself on Adobe Experience Manager (AEM) as a Cloud Service, and it hosts AEM 6.5 for customers through Adobe Managed Services (AMS). A partner's managed service is a run team that covers what Adobe doesn't: your code, releases, authors, integrations and daily fixes.

This guide separates the two. It then covers what a partner run-service should include, how service level agreements (SLAs) are usually written, what drives cost and how to choose a provider.

What does "AEM managed services" actually mean?

It's one phrase with two owners. "Adobe Managed Services" is an Adobe product name. Adobe's AEM 6.5 Long-Term Support (LTS) documentation describes it as AEM "deployed and managed by Adobe Managed Services", with environments run through Cloud Manager. Partners use "managed services" for a different thing: a contract to run, support and improve your AEM estate after launch.

The two often sit side by side. A company on AMS still needs someone to own its custom components, its Dispatcher rules (AEM's caching and request-filtering layer) and its integrations. A company on AEM as a Cloud Service has no servers to patch. It still has a code base, a release process and a few hundred authors who need help on a Monday morning.

So when a colleague says "we need AEM managed services", ask one question first. Do they mean hosting and platform operations, or the people who keep the site, its code and its content running? It's usually the second, and that's what most of this guide covers.

What does Adobe operate in each AEM deployment model?

Adobe runs the most on Cloud Service and Edge Delivery Services. It runs a fair amount on AMS and almost nothing on a self-hosted install. Here's the split before the detail.

AEM as a Cloud Service

Adobe's Experience League documentation says that with Cloud Service "Adobe is responsible for many aspects" of running AEM. The architecture scales with real traffic, maintenance updates arrive automatically, and new features switch on monthly. Backups are Adobe's too. Cloud Manager can restore content from point-in-time backups in the last 24 hours, or from system backups in the last seven days.

Your application isn't Adobe's job. Your code must live in the Cloud Manager Git repository and stay compatible with the latest AEM baseline image. It also has to pass the pipeline's quality, security and performance gates. Your own functional tests run during Adobe's updates too, and Adobe says a release doesn't proceed if checks fail. Adobe's roadmap warns that environments more than six months behind need scheduled updates with Adobe's help.

Adobe Managed Services

AMS hosts AEM 6.5 in the cloud for you. Adobe's AEM 6.5 documentation says Adobe "manages the cloud architecture". Cloud Manager for AMS adds continuous integration and delivery (CI/CD) pipelines with code inspection, security and performance checks. Your named Adobe Customer Success Engineer (CSE) is the contact for things like autoscaling.

Your code, components and integrations are still yours. Before you scope a partner, ask Adobe to confirm in writing which operational tasks your AMS contract covers. Contracts differ, so don't assume.

On-premises AEM 6.5 LTS

On-premises is, in Adobe's words, AEM "deployed and managed in your corporate environment". Adobe supplies the software, service packs and product support. Every operational task, from the operating system and Java to backups, Dispatcher and the CDN, belongs to you or your partner.

Edge Delivery Services

Edge Delivery Services replaces the AEM publish tier and Dispatcher with what Adobe calls "a multi-cloud SaaS solution". Adobe runs it on a CDN and serverless infrastructure, and it works with the included Adobe-managed CDN or your own. Code lives in GitHub as plain HTML, CSS and JavaScript, so the front end, its speed and its bugs belong to your team or partner. If you're weighing a build on it, our Edge Delivery Services partner list is a starting point.

What does Adobe support cover, and where does it stop?

Adobe support fixes product problems. It doesn't maintain your custom code or answer every author's how-to question. Knowing where that line sits is the main reason to scope a partner service carefully.

Every Adobe Experience Cloud licence includes the Expert Success plan. It gives 24x7 help for priority 1 (P1) issues, meaning production is down, and business-hours help for P2 to P4. The paid Ultimate Success plan adds a designated Technical Account Manager and Customer Success Manager, faster targeted response times, and upgrade and release preparation reviews. Adobe also sells an Advanced Cloud Support add-on for AEM as a Cloud Service.

Two details shape any run-service. First, Adobe works with a fixed list of Named Support Contacts: four per product on Expert and up to 15 on Ultimate. If someone outside that list opens a case, Adobe may ask for it to be resubmitted. Put your partner's service leads on the list, or agree who files tickets.

Second, Adobe's uptime SLA covers Adobe's side of the service. Cloud Manager's SLA reports measure author and publish uptime "factoring incidents caused by Adobe or Adobe's vendors". A 99.99% publish tier commitment exists, but only with both the Additional Publish Region and 99.99% SLA add-ons. An outage caused by your own code doesn't count against Adobe. That's the gap a partner SLA fills.

What does a partner AEM run-service cover?

A good run-service covers everything between "the platform is up" and "the business is getting what it needs from the site". The scope usually falls into six areas.

Author support and content operations

Authors need a help desk that knows your components, templates and workflows, not generic AEM training. Many contracts add content operations too: building pages, publishing campaigns, and managing Experience Fragments or translations when your own team is stretched.

Releases and Cloud Manager pipelines

The partner owns the release train. That means code review, merges, running full-stack, front-end and config pipelines, and fixing quality-gate failures before they block a release. On Cloud Service they also track Adobe's calendar. The roadmap lists feature release 2026.10.0 for October 29, 2026. It also pauses automatic maintenance from November 23 to December 1, 2026, and again from December 14, 2026 to January 3, 2027. Our note on the AEM 2026.9.0 release shows what a typical month asks of a run team.

Monitoring and incident response

Adobe watches the platform, but someone has to watch your application. That means error rates, slow templates, stuck workflows and failing integrations. A partner should run its own alerting on logs and synthetic checks, then triage each incident. It should open an Adobe case only when the fault really sits on Adobe's side.

Updates, upgrades and service packs

On Cloud Service, this means keeping custom code compatible with each AEM update and fixing whatever blocks one. On AMS or on-premises, it means planning and testing each 6.5 LTS service pack. Adobe's roadmap lists Service Pack 4 for February 18, 2027.

Security and configuration

This covers Dispatcher rules, CDN settings and traffic filter rules, including web application firewall (WAF) rules, which Cloud Service deploys through the config pipeline. It also covers user and group hygiene, secrets and dependency patching. On-premises, add the operating system and Java.

Small enhancements

Most contracts include a monthly pool of hours for new components, template changes and integration tweaks. Agree up front how the pool is used and when a request becomes a separately priced project.

How are AEM managed services SLAs usually structured?

Most partner SLAs promise response and resolution targets by priority, not uptime. On Cloud Service, uptime is Adobe's commitment, so a partner promising 99.99% for your whole site should explain exactly what they'd control.

Here's what buyers commonly see in partner contracts:

• Four priority levels, often close to Adobe's P1 to P4 definitions so tickets translate cleanly between the two.
• A response target plus a separate target for a workaround or fix. Response alone is easy to promise.
• Coverage hours by priority, such as round-the-clock cover for production outages and business hours for the rest.
• A rule for issues that turn out to be Adobe's, where the partner's clock pauses once a well-documented Adobe case is open.
• A monthly report on tickets, releases, incidents and hours used, reviewed with a named service manager.

Some contracts include service credits. Many rely on reporting and quarterly reviews instead. Either way, read three clauses closely. Watch for "best efforts" wording on P1, P1 targets measured only in business hours, and exclusions for anything touching an integration. Each one quietly weakens the promise.

What drives the cost of AEM managed services?

Adobe doesn't publish partner rates, and partners price on scope, so there's no honest "typical" monthly figure. These drivers move a quote up or down:

Most providers sell a monthly retainer with a ticket or hours allowance. Larger estates sometimes buy a dedicated team instead. If you're considering a mixed onshore and offshore model, our page on offshore AEM delivery covers the engagement shapes.

What changed for AMS and AEM 6.5 customers in 2026?

If you're on AMS or self-hosted AEM 6.5, your run-service now has a deadline attached. Adobe's releases roadmap says classic 6.5 support for AMS customers ended by August 31, 2026. Core support for on-premises customers is planned to end in February 2027. Adobe's support article dates on-premises core support to February 28, 2027, with extended support for critical fixes to February 28, 2028.

AEM 6.5 LTS, first available in March 2025, is where 6.5 support continues. It supports Java 17 and 21 and gets regular service packs, and Adobe recommends planning the upgrade. For many 6.5 estates, "managed services" in 2026 really means three jobs. Keep the site running, finish the LTS upgrade, and decide whether to move to Cloud Service. Ask providers to price those separately.

Some teams use this moment to ask whether they should leave AEM altogether. Our guide to moving from AEM to WordPress covers when that makes sense and when it doesn't.

How do you choose an AEM managed services partner?

Choose on run evidence, not build portfolios. The firm that built a great site may not want the 2 a.m. call.

Start with what Adobe validates. Adobe's Solution Partner Program offers an Experience Manager Run & Operate specialization alongside Sites and Assets. Adobe's guidelines let a firm count "a run and operate engagement" as a customer reference. Each specialization needs certified staff, and renewing it every two years needs fresh references. Check who holds it in Adobe's own Partner Directory, and read what Adobe partner tiers measure before you lean on any badge.

Then test the operation itself:

• Ask to see a real monthly service report, redacted.
• Ask who's on call this weekend, by role and time zone.
• Ask how they handled the last AEM update that failed a quality gate.
• Ask for the onboarding plan: access, runbooks, a code health check, and the date the SLA starts.
• Ask what you get at exit: documentation, credentials and a handover period.

Plan a transition period before the SLA fully applies. The new team needs access to Cloud Manager, Git, the Adobe Admin Console and your monitoring. It then needs time for a code health review and a list of known issues. Expect the first monthly report to be mostly findings, and that's a good sign.

If another firm built your site, keep it involved during that overlap. If you still need a build partner too, our guide to AEM implementation partners covers that side. The comparison tool then puts shortlisted firms side by side.

What to do next with AEM managed services

• Write one page on your deployment model and what your Adobe contract covers.
• List the run tasks Adobe doesn't do, using the six areas above.
• Agree priority definitions and coverage hours before you ask for prices.
• Confirm who your Named Support Contacts are and add the partner's leads.
• If you're on 6.5, put the LTS upgrade and the Cloud Service decision in the same plan.
• Send three providers the same brief and ask each for the same evidence.
• In our directory, use the Managed Services capability filter to narrow the AEM list.

Start that shortlist with the AEM partners in our directory and send each the same scope with our AEM request for proposal (RFP) template.