Skip to main content
ANNOUNCEMENTMeet MariaDB Enterprise Platform 2027. Read more.

Menu

WEBINAR

Built for the Agentic Era: Introducing MariaDB Enterprise Platform 2027

Register now

Product

MariaDB Cloud AI Retrieval: Managed RAG over Documents and Databases

By Egor Ustinov

12 min read
Share

Key takeaways

  • MariaDB Cloud AI Retrieval is a managed retrieval-augmented generation (RAG) service in MariaDB Cloud, now in Public Preview, that lets teams ship AI applications and agents without building or operating their own retrieval stack.
  • A Document Knowledge Base turns documents such as PDF, DOCX, and PPTX into answers with citations, using managed parsing, chunking, embedding, hybrid search, and reranking.
  • A Database Knowledge Base turns natural-language questions into read-only SQL against the MariaDB database, so operational data isn't copied into a separate vector store or warehouse.
  • Developers query both knowledge base types through a simple REST API.
curl -X POST "$API_BASE/ai/v1/knowledge-bases/$KB_ID/retrieve-rows-and-generate" \
-H "X-API-Key: $MARIADB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "Which customers renew this quarter?",
"execute": true,
"max_rows": 20
}'
curl -X POST "$REGION_API_BASE/ai/v1/knowledge-bases/$KB_ID/retrieve-chunks-and-generate" \
-H "X-API-Key: $MARIADB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"enable_rerank": true,
"query": "What does Globex's contract allow on price increases at renewal?",
"retrieval_method": "hybrid",
"top_k": 30,
"llm_provider": "bedrock",
"llm_model": "anthropic.claude-sonnet-5",
"temperature": 0.3,
"top_p": 1,
"max_tokens": 8192
}'

Teams delivering AI applications and agents that need grounded answers from documents, MariaDB data, or both. Engineering and data leaders use it to shorten time to market and avoid a second copy of their data; AI builders call its REST API from any framework.

Yes. MariaDB stores embeddings in a native VECTOR data type with a vector index, alongside your transactional tables. A Document KB can use an existing MariaDB Cloud service as its vector store; for heavy ingestion or query volume, size that service for both workloads or give the knowledge base a dedicated one.

Yes. Create a Document KB per tenant on the same MariaDB service. Each knowledge base stores its data in its own schema, and each retrieval request targets one knowledge base by ID, so one tenant’s documents aren’t returned for another tenant’s queries. Your application maps each tenant to its knowledge base.

No. A Database KB stores a semantic map of the schema and runs read-only SQL against the live database at query time. A Document KB stores document chunks and embeddings in a MariaDB database in your own MariaDB Cloud account.

No. Generated SQL is validated as read-only before it runs, and results are capped by a row limit.

PDF, DOCX, PPTX, HTML, TXT, Markdown, and JSON. Layout-aware parsing preserves tables, headings, lists, and reading order in digital-source documents.

Yes. The Retrieve call returns ranked chunks or rows without generation, so any model or framework that can make an HTTP request can use them. Retrieve & Generate calls the LLM for you, with the model set per request.

During Public Preview, every MariaDB Cloud account gets a free allowance of 100 MariaDB Compute Units (MCUs) per month for AI Retrieval, enough to evaluate both Document KBs and Database KBs.