Chapter 1. AutoRAG overview


AutoRAG is an automated optimization system in Red Hat OpenShift AI that finds the best retrieval-augmented generation (RAG) configuration for your documents and use case. You provide documents and test data. AutoRAG tests different RAG configurations, ranks results by evaluation metrics, and generates notebooks to run RAG patterns.

1.1. AutoRAG workflow

When you create an AutoRAG optimization run, AutoRAG tests combinations of chunking, embedding, retrieval, and generation settings against your test data. Each combination produces a RAG pattern with evaluation scores. AutoRAG ranks patterns on a leaderboard and generates Jupyter notebooks that you can use to run the best pattern.

AutoRAG automatically samples up to 1 GiB of relevant documents based on your test data, so you do not need to filter your document set in advance. Documents referenced in your test data are prioritized during sampling.

1.2. AutoRAG terminology

RAG pattern
An optimized RAG configuration that includes performance metrics, a leaderboard position, and indexing and inference notebooks.
Search space
The set of parameter combinations that AutoRAG tests during optimization. The search space includes chunking, embedding, retrieval, and generation settings.

1.3. Technology Preview limitations

Important

AutoRAG is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. For more information, see Technology Preview Features Support Scope.

The following limitations apply during Technology Preview:

  • Only English language documents are supported.
  • Remote Milvus vector databases only. Inline Milvus is not supported.
  • A maximum of three foundation models and two embedding models per optimization run. Specifying more models can cause the run to fail.
  • Images embedded in documents are not processed.
  • Optical character recognition (OCR) is not available for PDF documents.
  • Table structure detection is not available for PDF documents.

1.4. Viewing externally created runs

If you import an AutoRAG pipeline to your pipeline server and create runs from it, the runs appear on the AutoRAG page in the dashboard. When you import the pipeline, set the pipeline name to documents-rag-optimization-pipeline and the pipeline version name to documents-rag-optimization-pipeline-<version>, such as documents-rag-optimization-pipeline-3.4.0.

For more information about importing pipelines, see Importing a pipeline.

To find the best RAG configuration for your documents, prepare test data, create an AutoRAG optimization run, evaluate the results, and run the best-performing pattern.

Before you begin, ensure that the following prerequisites are met:

  • A Llama Stack instance is available and configured with foundation and embedding models. For more information, see Working with Llama Stack.
  • A remote Milvus vector database is registered with your Llama Stack instance. Inline Milvus is not supported.
  • Your documents are available in an S3-compatible storage bucket or locally for upload.
Important

Upload the updated AutoRAG pipeline definition before you create your first run. For instructions and download links, see RHOAIENG-64768 - AutoML and AutoRAG pipeline runs fail with image pull errors in the release notes.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top