Ship a RAG chatbot on your database — embeddings stay yours.

Retrieval-augmented generation as ordinary endpoints on a database you already run. Ingest your documents, store the embeddings next to them, and answer questions from your own data — with no third-party vector store in the middle.

RAG without a proprietary vector silo

The embeddings live in your database, beside the documents they came from. There's no separate vector service to sync, secure, pay for, or explain to your compliance team — and nothing about your corpus has to leave your infrastructure.

Two paths, same shape

The RAG Chatbot pack runs on Postgres with pgvector. The MongoDB Atlas Vector Search RAG pack does the same on Atlas. Fork whichever matches the database you already have — the endpoints look the same either way.

Ingest, chat, history, delete

A chatbot is a handful of endpoints, so that's what you get: seed and ingest documents, chat against them, read history, and delete. They're readable config — extend them like any other Air Pipe interface.

Observable, like every other endpoint

Retrieval is where RAG quietly goes wrong. Every call ships OpenTelemetry traces and Prometheus metrics automatically, so you can see what was retrieved and how long it took — rather than guessing why an answer was poor.

Frequently asked questions