Renbase¶
Renbase is a context layer for AI agents and support chats. Your documents and your business definitions live in one corpus, versioned and approved by your team, and every answer built on them carries its sources.
The rule is simple: an answer you can defend, or "I don't know".
What it does¶
- Answers questions from your content. People ask in natural language, in the workspace or through the API, and get an answer drawn from your documents and your approved definitions.
- Cites every claim. Each answer carries typed citations: which document or definition it came from, which version, who approved it and when it was last verified.
- Abstains instead of inventing. When the supporting content is missing, expired or contradictory, Renbase says so. It does not fill the gap with a plausible guess.
- Serves your AI agents. Any MCP-compatible agent consults the same corpus, under the same rules, keys and usage accounting as your people.
Where to start¶
| If you want to… | Go to |
|---|---|
| Ask your first question in five minutes | Quickstart |
| Learn the workspace, screen by screen | Workspace tutorial |
| Understand documents, definitions and approval | Core concepts |
| Upload and manage content | Documents |
| Govern the definitions that shape answers | Business definitions |
| Connect Claude or another agent | AI agents (MCP) |
| Compare with AWS, Google Cloud and Azure RAG | vs. managed RAG |
| Run Renbase inside your own infrastructure | Enterprise (BYOC) |
| Look up an endpoint | API reference |
The answer contract¶
Everything in Renbase follows the same three rules, and they are worth stating before anything else:
Sources, always. An answer with no source is not an answer. Every claim is anchored to an approved definition or an ingested document, with its version and its provenance travelling alongside.
Human approval before serving. Definitions proposed by an import or generated automatically arrive as drafts. Nothing shapes an answer until someone on your team approves it.
Silence over invention. If no source supports the question, the answer says so. If two approved definitions contradict each other, both are returned, marked as conflicting. The choice is never made quietly on your behalf.
Getting access¶
Renbase is multi-tenant: each organization has its own corpus, members, keys and usage. Your organization's admin invites members by email (they sign in with a one-time code, no passwords) and issues the API keys used by services and agents.
If you don't have an organization yet, contact the team at [email protected].
For organizations whose corpus can't leave their own infrastructure, Renbase also deploys inside your cloud — see Enterprise (BYOC).