Each update tried
before it reaches you
We build, upgrade and move Adobe Experience Manager sites, from 6.5 to 6.5 LTS or the cloud service, with tests that run before each update, so changes are tried before your visitors see them.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When nobody knows what an upgrade will touch
Many Adobe Experience Manager sites have run on 6.5 for years, with custom components, services, workflows and integrations built around them. Some of that code may rely on features or APIs that 6.5 LTS or the cloud service no longer include: Adobe lists what each one has removed, and how much a site uses varies.
So an upgrade starts by finding what each piece relies on, and it waits while no one is sure.
On the cloud service, Adobe updates the platform itself, often. The tests your team writes are what check each update against your own code, and where a build has none, that step passes on its own.
What we build
Every customization and integration on your sites listed with the person who owns it, and every upgrade and move tried on a copy first, a separate environment kept for testing, before your authors or visitors see it.
Sites on the cloud service
Sites built as Adobe sets out for the cloud service, on its project archetype, with Core Components, HTL and Sling Models, and deployed through the pipelines in Cloud Manager. The Java behind them is written and tested to the standard of our Java Development work.
Edge Delivery Services
Blocks written in plain HTML, CSS and JavaScript from Adobe’s boilerplate, each one a table your authors fill in, in a document or in the Universal Editor, and shown as its part of the page. They’re built the way our Web & App Development work builds any front end.
From 6.5 to 6.5 LTS
Each site upgraded to 6.5 LTS as Adobe’s upgrade guide sets out, on Java 17 or 21, with its code checked for what 6.5 LTS no longer includes, using Adobe’s own analyzer, and tried on a copy first.
Moves to the cloud service
Code refactored to the cloud service’s rules, found with the Best Practices Analyzer, and content carried over with the Content Transfer Tool, tracked in Cloud Acceleration Manager. Site by site, as your setup allows.
Tests for every update
Custom functional and UI tests, run in the quality gates in Cloud Manager, so each of Adobe’s updates is checked against your code before production, as the next section shows.
Components your authors arrange
Core Components, editable templates, policies and the Style System, with content fragments and experience fragments, so authors build pages from parts within the rules set for them.
Many sites and languages
Sites rolled out from one blueprint as live copies with Multi Site Manager, kept within one language as Adobe advises, and language copies translated through translation projects.
Integrations
Content fragments delivered through GraphQL, Adobe’s APIs for your other systems, and changes sent through Adobe I/O Events to code that runs in App Builder, each integration with only the access it needs.
AI where it helps
On the cloud service, Adobe’s agents and its MCP server, which work within the permissions of the person who signed in. Adobe’s pages say the agents aren’t currently available on 6.5 LTS.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Developers in your own team:Hire developers for Adobe Experience Manager sites
Each update meets your tests first
On the cloud service, Adobe updates the platform itself. New features come in a monthly release, and fixes and security updates in maintenance releases twice a month, each published a few days before it reaches your environments.
Each update goes to development first, then to stage and production, and the tests your team writes run on the way. Adobe’s docs set out that if one of your functional or UI tests fails, the update isn’t rolled out to production.
So the tests are part of the build, written for the pages and paths that matter most. On 6.5 LTS, your team applies each service pack itself, tried on a copy first.
{{ upAns }}
Production gets an update only after the checks on the way pass, your tests among them.
{{ upStatus }}
Run it yourself, or let Adobe run it
Adobe offers the platform two ways today: as a cloud service, which Adobe runs and keeps on its latest version, and as 6.5 LTS, on your own servers or on Adobe Managed Services, which continues the 6.5 line on Java 17 and 21.
For classic 6.5, Adobe has set its dates. Support on Adobe Managed Services ended by August 31, 2026. On your own servers, core support is currently planned to end by February 2027, February 28 in Adobe’s knowledge base, with extended support for critical fixes until February 28, 2028, and 6.5.26.0, targeted for November 19, 2026, is its last service pack.
6.5 LTS takes service packs on Adobe’s roadmap: the latest, SP3, came out on August 20, 2026, and SP4 is targeted for February 18, 2027. On the cloud service, Edge Delivery Services can serve your pages, enabled for a project in Cloud Manager.
So each site is kept on a version Adobe supports, and a move to the cloud service is planned site by site, when it suits the business.
Start with what the code relies on
The review covers each site: its version and service pack, its hosting, your own servers, Adobe Managed Services or the cloud service, and where it stands on Adobe’s roadmap; the custom code, its bundles, services, servlets, workflows and scheduled jobs, what each one does and which APIs it relies on, checked with Adobe’s own analysis tools where Adobe offers them; the components, Core Components or custom ones, the templates, static or editable, and their policies, and which ones your authors can arrange today; the content fragments, experience fragments and assets your pages use; the sites and languages, their live copies, language copies and translation; the Dispatcher and caching rules; each integration, what it reads and writes, its access and the APIs it uses; the tests, what exists and what an update would be checked against today; and roles, workflows and publishing.
The first step is one of four, tried on a copy first: one site’s code checked and built against 6.5 LTS or the cloud service, tests written for the pages and paths that matter most, one component rebuilt on Core Components, or one Edge Delivery Services block on one page.
You get a written review and a proposal for the first step.
Questions worth asking
Should we move to 6.5 LTS or to the cloud service?
The answer turns on your custom code, your team and where you host today. Adobe continues 6.5 support through 6.5 LTS, on your own servers or on Adobe Managed Services, while on the cloud service Adobe runs the platform and updates it for you. Some companies take every site to 6.5 LTS now and plan the cloud service later; others move one site first. We lay out both routes for your sites, and the choice and its timing stay yours.
What do Adobe’s dates mean for our 6.5 site?
Your site keeps running; what changes is what Adobe provides for it. On Adobe Managed Services, support for classic 6.5 ended by August 31, 2026. On your own servers, core support is currently planned to end by February 2027, February 28 in Adobe’s knowledge base, with extended support for critical fixes until February 28, 2028, and 6.5.26.0, targeted for November 19, 2026, is the last service pack. 6.5 LTS continues the line on both. We check where your site stands and plan its next step, tried on a copy first.
What does upgrading to 6.5 LTS involve?
Adobe’s release notes and upgrade guide set it out. 6.5 LTS runs on Java 17 or 21, and while it aims to stay compatible, some older features are gone, Communities and Screens among them, and Guava is no longer part of the platform. Adobe’s analyzer shows what your code relies on, and a site on 6.5 can upgrade straight to a 6.5 LTS service pack. We run it on a copy of your site, with its custom code, before it reaches the live site.
How do updates work on the cloud service?
Adobe ships them. New features come in a monthly release and fixes in maintenance releases twice a month, each applied to development first, then stage, where your tests run, and only then production. If one of your functional or UI tests fails, the update isn’t rolled out. Where a build has no tests of its own, that step passes, so we write them for the paths that matter most.
What is Edge Delivery Services, and do we need it?
It’s part of the platform: a way to serve pages from blocks your developers build in plain HTML, CSS and JavaScript, while your authors write in documents or in the Universal Editor. On the cloud service it’s enabled for a project in Cloud Manager, and it can sit beside your existing pages on the same domain. Whether it suits you depends on your sites and how your authors work, so we try it on one page first.
Can our authors build pages without a developer?
Yes, within the parts and rules set for them. With Core Components, editable templates and their policies, authors add and arrange components on their pages; with Edge Delivery Services, they write in documents or in the Universal Editor and the blocks shape the page. We build the parts and set what each template allows.
Can one instance run all our sites and languages?
Often, yes. Multi Site Manager rolls content out from a blueprint to live copies, the local sites, and Adobe advises keeping it within one language. Language copies, translated through translation projects, carry each site into other languages. Where to share and where to let each site differ is a choice for your brands and markets, and we plan it with your teams.
Can you connect it to our CRM, commerce or other systems?
Yes. Content fragments can be delivered through GraphQL, Adobe’s APIs reach your other systems, and Adobe I/O Events sends changes, such as a content fragment updated, to code that runs in App Builder, outside the platform. Before anything is connected we settle which system is in charge of each record, and each connection gets only the access it needs and a trial run on a copy.
Can AI assistants work with our pages and content?
On the cloud service, yes, in the ways Adobe offers. Its MCP server lets an assistant work with pages, content fragments and assets under the identity of the person who signed in, within their existing permissions, and Adobe’s agents work alongside your team. Adobe’s pages say the agents aren’t currently available on 6.5 or 6.5 LTS, nor on Adobe Managed Services. Each assistant gets only the access its work needs, and we set it up that way.
Will our hosting change?
Only if you decide to move. On 6.5 LTS your sites stay where they run now, on your own servers or on Adobe Managed Services. On the cloud service, Adobe runs the platform, and your code reaches it through the pipelines in Cloud Manager. For servers you keep yourself, our Cloud, DevOps & Security work sets them up and looks after them.
Can you take over our existing site?
Yes. We start with the review, learning what your code relies on and who looks after each part, then take on the first piece of work you choose, alongside your own developers where you have them.
How do you keep our sites secure?
On 6.5 LTS, Adobe’s security fixes come in service packs and hotfixes, listed in its security bulletins, and we apply each one on a copy first. On the cloud service, Adobe’s updates carry them. Who can edit and who can publish is set by roles and workflows, and no integration reaches more than it needs.
What does it cost?
It depends on your sites, the custom code around them and the first step you choose. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.
Can we hire developers for our own team?
Yes. We introduce developers who know the platform within 48 hours of your request, working in your time zone. You meet them first, and decide who joins.
Adobe and Adobe Experience Manager are either registered trademarks or trademarks of Adobe in the United States and/or other countries, and the other Adobe product names on this page may be trademarks of Adobe. Webair is independent of Adobe, and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us the version and hosting each of your sites runs on. We’ll agree on a first step in a short call.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}