Enterprise search for Adobe AEM
Adobe Experience Manager manages your content; it does not ship a faceted, semantic search experience out of the box. Viglet adds one, open source and self-hosted: Viglet Dumont connects AEM and indexes it into Viglet Turing, which serves faceted navigation, semantic and vector search, and cited RAG answers over your AEM content.
How they compare
Objective differences on the dimensions that decide a search platform.
| Viglet on AEM | Hosted SaaS search | |
|---|---|---|
| AEM connector | Dumont connector for Adobe AEM (and Adobe Edge Delivery Services) | Vendor connector or a custom crawler |
| License | Open source, Apache 2.0 | Proprietary / commercial |
| Deployment | Self-hosted from one Docker image, alongside your AEM environment | Vendor-hosted SaaS |
| Where content lives | Inside your own perimeter. AEM content and queries never leave it | The vendor cloud |
| Faceted search | Faceted, multilingual, typo-tolerant on Solr, Elasticsearch or Lucene | Provided by the vendor |
| Semantic & vector search | Built in: hybrid keyword + vector ranking (RRF) | Available, varies by plan and vendor |
| Generative answers (RAG) | Built in, with citations. Bring your own LLM | Available, varies by vendor |
| Pricing model | No per-document or per-query fees | Usage-based: priced per record, query or request |
Comparison column describes hosted SaaS search in general terms; capabilities and pricing vary by vendor and plan. See the guides below for detailed, vendor-by-vendor breakdowns.
The Viglet approach
Index AEM with Dumont
The Dumont connector for Adobe AEM (and Adobe Edge Delivery Services) extracts pages and assets and normalizes them into one flow. Per-field coverage and drift monitoring catch silent layout changes.
Serve faceted, semantic search with Turing
Turing indexes the AEM flow into Apache Solr, Elasticsearch or Lucene and adds faceted, multilingual navigation plus embedding-based vector search over your AEM content.
Answer questions over AEM content
A RAG chatbot returns answers grounded in your AEM content with citations, using the LLM you choose, on your own infrastructure.
Guides & comparisons
Step-by-step how-tos and vendor-by-vendor comparisons on the Viglet blog.
How to Add Enterprise Search to Adobe AEM with Viglet Turing
A step-by-step guide to indexing Adobe Experience Manager content into an open-source enterprise search engine with faceted navigation, semantic search, and RAG: an alternative to Algolia, Coveo, and Lucidworks.
Semantic & Vector Search in Adobe AEM with Viglet Turing
Go beyond keyword search on Adobe Experience Manager content: add embedding-based vector search and semantic navigation with an open-source platform, on your own infrastructure.
Open-Source Alternatives to Algolia and Coveo for Adobe AEM
Comparing search options for Adobe Experience Manager: Algolia, Coveo, Lucidworks, raw Solr/Elasticsearch, and the open-source Viglet Turing. Pricing model, data residency, facets, semantic search, and RAG.
Common questions
Does AEM not already have search?
AEM includes full-text query capabilities for authoring and delivery, but not a turn-key faceted, semantic, typo-tolerant search experience with RAG answers. Viglet adds that layer on top, indexing AEM content into Turing.
How does Viglet get content out of AEM?
Dumont has a ready-to-use connector for Adobe AEM (and Adobe Edge Delivery Services). It extracts pages and assets into a flow and delivers them to Turing, Apache Solr or Elasticsearch. You do not write a custom connector.
Can I add semantic and vector search to AEM?
Yes. Turing adds embedding-based vector search and semantic navigation over indexed AEM content, combined with keyword ranking (RRF), all self-hosted.
Where does the AEM content end up?
On your own infrastructure. Turing and its search engine run from Docker inside your perimeter, so AEM content and user queries are never sent to a vendor cloud.
Own your search: open source, self-hosted
Free under Apache 2.0, deployed from a single Docker image.