Skip to main content
Level 2
Oct 5, 2026 2:07 PM UTC
Question

Has anyone implemented SSR with AEM 6.5 On-Premise + Vue.js?

Hi,

Has anyone successfully implemented Server-Side Rendering (SSR) with AEM 6.5 LTS and Vue.js (Vue3)?

I would appreciate if anyone can share me any lead 

1 reply

Level 2
Oct 9, 2026 5:04 PM UTC

​@PrakashBa2 ,

AEM can’t run Vue on the server itself (6.5 LTS or Cloud Service). Rhino doesn’t support modern JS and Nashorn was removed in Java 15, so Vue 3 SSR needs a separate Node renderer outside AEM.

I would prefer using the the Remote Content Renderer (RCR). AEM POSTs the page model to your Node service, which renders it with createSSRApp + renderToString and returns HTML. The client then hydrates. You need two webpack builds: the client one goes into the clientlib, and the server one is deployed to the Node service. Adobe documents RCR for React and Angular only, so for Vue you’d write the renderer yourself extensively. The design would be something similar to :

 

Sample Design

Things to watch:

  • The SPA Editor is deprecated, and the Vue community packages (Vue 2 @mavice, Perficient’s Vue 3 port) don’t include an SSR pipeline.
  • If you host on Adobe I/O Runtime, there are limits: 60 s timeout, 1 MB payload, 600 activations/min.
  • Keep author mode client-side, and watch for hydration mismatches.

Alternatives: If Vue only handles interactive parts, render the SEO-critical markup in HTL and let Vue enhance it, with no Node service needed. For a Vue-heavy build, a decoupled Nuxt 3 app with persisted GraphQL queries and the Universal Editor is a cleaner option.

Translate