Viglet Turing
Search your content. Answer with sources.
Add faceted search, cited RAG answers and AI agents to your site or application, with your choice of search engine and model.
Try Turing liveInstall TuringStart with Viglet Turing for search and cited answers. Connect existing sources with Dumont, or manage content with people and AI agents in Shio.
Choosing a CMS or connector? Find your product.
How do I index Adobe AEM content?
Configure a Dumont AEM source to extract pages and assets, then deliver the mapped content to Turing for search.
Read the source
AEM integration guideWritten examples. The live playground searches Turing documentation.
Try the live playgroundThree independent products. Add an integration when your project needs it.
Viglet Turing
Add faceted search, cited RAG answers and AI agents to your site or application, with your choice of search engine and model.
Try Turing liveInstall TuringViglet Dumont
Extract and map content from AEM, databases, files and websites into Turing, Solr or Elasticsearch.
Explore Dumont connectorsInstall DumontViglet Shio
Manage content in the console or through an AI agent over MCP. Publish pages or deliver content to your application through REST and GraphQL.
See Shio with an agentInstall ShioAnswer three questions and get the product, or the combination, that fits. Or compare all three side by side.
See search and cited answers over WKND content, then follow the connector setup for your AEM environment.
Explore the AEM demo →Read the AEM integration guideFollow the WordPress integration guide. You will need a Turing server; AI answers also require a configured model.
Read the WordPress guide →Set up the Turing serverConnect Claude Code to Shio through MCP and see how content authoring and review fit together.
Read the Shio agent guide →Explore Shio for agentsEach path is optional. You do not need all three products to get started.
AEM, databases, files and websites
Turing search and cited answers
Dumont feeds supported sources into Turing. It can also deliver directly to Apache Solr or Elasticsearch.
Content managed in Shio
Turing search and cited answers
Add Turing when a Shio site needs search and answers over its content.
People and agents author content
Your website or application
Use Shio as a CMS on its own. Turing and Dumont are not required to publish content.
Use the content sources, search engine and LLM you already have.
Sources
Search engines
AI & LLMs
Delivery
Short, direct answers.
No. Each product runs on its own: Viglet Turing for search and AI, Viglet Dumont to feed it content, and Viglet Shio to model and serve content. They also work together, but there is no lock-in and no required bundle.
Match the product to the job: Viglet Dumont extracts and moves data (indexing, ETL, connectors); Viglet Shio models and serves content (CMS, sites, delivery API); Viglet Turing searches and answers (enterprise search, semantic navigation, AI chatbot).
Yes. Viglet Turing is open-source enterprise search under the Apache 2.0 license. You self-host it without per-document or per-query license fees, and it includes faceted search, semantic/vector search and generative AI (RAG).
One Docker command per product, pulling the image from the GitHub Container Registry (ghcr.io). The runtime is bundled in the container, so no separate Java install is needed; configure storage, sources and any model providers for your deployment. To have Viglet host it for you instead, Viglet Cloud is in beta at viglet.cloud.
Viglet Dumont connects Adobe AEM, WordPress, SQL databases, file systems and any website through its web crawler, and delivers the content into Apache Solr, Elasticsearch or Viglet Turing.
Yes. Viglet Turing includes vector/semantic search and Retrieval-Augmented Generation with the LLM of your choice (OpenAI/ChatGPT, Ollama, Anthropic or Google Gemini), on SaaS or on-premises. Answers are grounded in your indexed content, with citations.
There are no product license fees. Your team runs the infrastructure, configures persistent storage, manages backups and updates, and pays for any external models or services it enables. For help planning a deployment, contact Viglet about implementation and support options.
You control where the application and indexed content are hosted. To keep processing within your infrastructure, configure local models and embeddings and review external integrations. Cloud model providers and external tools receive the data needed for the requests you enable.
Self-host it, or let Viglet host itBeta
Every product runs from one Docker image on your own servers. Or let Viglet run them for you on Viglet Cloud, which is in beta, so features may change.
Start with the setup guide, or talk with us about sources, architecture and implementation support.