About

One AEM platform for 130+ brand websites

A global multi-brand manufacturer, centralized on AEM as a Cloud Service and stable for more than six years.

We helped a global multi-brand manufacturer move its brand websites onto one centralized Adobe Experience Manager as a Cloud Service platform. Today, 130+ brand websites share one design system, the same components, and the same templates while keeping their own look and feel, and the platform is run by the same lean team that has built it since the start.

Six differently themed brand websites connected to one shared design-system platform

At a glance

130+ brand websites

Every brand runs on one shared design system, components, and templates, with its own visual identity. Some sites are small, others serve 60+ markets.

6+ years in production

The platform has run in production for more than six years and stays current with Adobe's AEM as a Cloud Service releases.

One lean, stable team

Three frontend and three backend developers and two QA engineers, supported by a solution architect, product owner, and Scrum Master. The same team since day one.

The challenge

A group with more than 130 brands needs every brand to look and feel distinct, while still running one efficient, governed digital platform. Building and operating separate websites per brand multiplies licences, hosting, operations, and development effort, and makes quality and security hard to keep consistent.

The goal was a single platform that scales to every brand without turning into a slow, overly customized system that needs an ever-growing team to maintain.

What we built

Centralized AEM as a Cloud Service

One AEM as a Cloud Service platform for all brands, kept close to the product rather than heavily customized.

  • Around 30 highly configurable components and shared templates for every brand
  • Brand-specific look and feel without forking code
  • Continuous Adobe updates without costly upgrade projects

Shared design system, decoupled frontend

A shared design system is the foundation of the platform. It defines the components, patterns, and design tokens every brand builds on, and lives in a frontend fully decoupled from AEM.

  • One design system, themed per brand through design tokens instead of separate code
  • Consistent quality, accessibility, and UX across 130+ websites
  • Frontend releases independent of backend changes

Supporting microservices around AEM

Integrations and business logic that do not belong in the CMS run as supporting microservices built around AEM.

  • AEM stays focused on content and experience management
  • Integrations scale and change without touching the core platform
  • Fewer customizations make updates safer and faster

Quality built into delivery

Two dedicated QA engineers and automated testing at every level keep releases predictable across 130+ websites.

  • Automated unit, integration, performance, and UI tests in the delivery pipeline
  • Shared components are tested once and reused across every brand
  • Stable, routine releases instead of high-risk launches

Results for the business

A very stable platform

More than six years in production, up to date with Adobe's releases, and without the instability that comes from heavy customization.

Lower total cost

Centralizing licences, operations, and the development team removes the duplication of running separate brand platforms.

A team that gets more productive, not bigger

A core team of eight supports 130+ brand websites. With AI in the daily workflow, it delivers more without growing.

Why it worked

Platforms like this rarely fail because of the technology. They fail when every new requirement becomes a customization, and when the answer to slower delivery is a bigger team. This platform stayed fast and maintainable because of a few deliberate choices:

  • Standard over custom: AEM is used as intended, so Adobe's updates keep landing without upgrade projects.
  • Clear boundaries: content management in AEM, presentation in the decoupled frontend, and integrations in supporting services.
  • Design system first: one shared design system keeps 130+ brands consistent, accessible, and fast to build.
  • Reuse by default: a new brand is a new theme and new content, not new code.
  • Continuity: the same senior team has owned the platform for years, and the solution architect who designed it still supports the client today, so architectural decisions stay consistent and knowledge stays in the team.

We wrote more about why adding developers often slows platforms down in The AEM Team Budget Trap.

Planning a multi-brand or multi-market AEM platform? Start with a free review of your current architecture.