Ground the answers in your own material. Managed knowledge bases with ModuleX-managed vector storage, or bring your own store — Qdrant, Pinecone, MongoDB Atlas, or Weaviate.
SlackOAuth or Bearer tokenstored once
StripeAPI keystored once
HubSpotOAuth or Bearer tokenstored once
NotionOAuth or Bearer tokenstored once
Retrieval, without standing up a pipeline. The managed path is the default, not the fallback.
A knowledge base in ModuleX is managed: you point it at your material and it becomes something the assistant and your workflows can search. Vector storage is handled by ModuleX — the modulexdb path — so there is no separate database to provision, size, or keep alive before you can ask a question against your own documents.
This matters most for the teams who need retrieval least dramatically. Answering support questions from your own help material, or grounding a draft in the docs you already wrote, are not research problems. They stall on infrastructure nobody wanted to own.
- Managed vector storage (modulexdb) — nothing to provision.
- Searchable from workflows and from the assistant.
Or bring the store you already run. Four supported, named exactly.
If your organization already operates a vector store, ModuleX connects to it instead: Qdrant, Pinecone, MongoDB Atlas, and Weaviate. That list is the whole list, and it is worth being precise about rather than gesturing at "and others" — knowing which four are supported is the entire question when you are deciding whether this fits your stack.
The choice is about where the vectors live, not about what you can do with them. A knowledge base backed by your own store is used the same way from a workflow or from the assistant as a managed one.
- Bring-your-own: Qdrant, Pinecone, MongoDB Atlas, Weaviate.
- Same behaviour whichever store backs the knowledge base.
Retrieval is a step, not the whole job. The point is what happens after the lookup.
A knowledge base earns its place when the thing that reads it can also act. Looking up the answer is the first half; drafting the reply, filing the issue, or writing the summary into the tool your team actually uses is the half that removes the work.
So retrieval sits alongside the connected tools rather than in front of them. The assistant searches your knowledge base and then continues into the same run — and the steps that write something still wait for your approval, exactly as they would if the material had come from anywhere else.
- Search your material, then act on connected tools in the same run.
- Write steps stay behind the approval gate.
Every kind of key, counted from the registry. The vault holds the credentials behind all 179 integrations.
Built for the teams that run on it. See the vault at work behind a real workflow.
Knowledge bases FAQ
No. ModuleX-managed vector storage is the default path, so a knowledge base works without you provisioning or maintaining anything. Bringing your own store is the option, not the requirement.