Security
The security model, in one page
Renbase serves context; your agent acts. That division of labor is the security model's foundation: Renbase holds the documents and definitions you decide to govern, and it never executes anything against your systems or holds their credentials.
Isolation by organization
The organization is the unit of isolation, and it is enforced in every store the platform uses: the dense vector index, the lexical index and the relational database. Every request, whether from a person, a service or an agent, is scoped to the organization behind its credential. Content from another organization is not filtered out of results; it is out of reach.
This isolation is not an enterprise add-on. Renbase is multi-tenant from its first commit, with per-organization credits and rate limits, which is also what makes it embeddable inside a SaaS.
Identity and credentials
People sign in with a one-time code sent to their email. There are no passwords to manage or leak. Members hold a role: admins invite, approve definitions and issue keys; readers ask questions.
Services and agents authenticate with API keys, issued per integration so each can be revoked on its own. Revocation takes effect immediately. Agents connecting over MCP operate under the same organization scoping, credits and limits as people. There is no separate access path for machines.
What travels, what doesn't
- Documents you choose to upload (PDF, DOCX, HTML)
- Definition drafts submitted by the client-side connector: names, schemas, descriptions
- Questions your people and agents ask, and the cited answers
- Your warehouse credentials: the connector runs on your machine and they never leave it
- Your warehouse's row data: Renbase neither runs nor generates SQL against it
- With BYOC: everything above too, because the whole platform runs in your infrastructure
The connector runs on your side
Schema introspection (reading your warehouse's structure to propose definitions) runs as a CLI on your machine, with your credentials, inside your network. What it submits to Renbase is draft entries: names, schemas, descriptions. Those drafts are invisible to answers until someone on your team approves them, so nothing a machine produced can reach an agent unreviewed.
BYOC: the platform runs in your infrastructure
For organizations whose corpus can't leave their perimeter, Enterprise runs bring-your-own-cloud: the entire platform (workspace, API, MCP endpoint and storage) deployed inside your infrastructure, guided by our team. Nothing about your corpus (content, questions, answers, usage) leaves it. All major clouds work, as does on-premises.
Security questionnaires
If your review needs more than this page (questionnaires, data-processing terms, deployment details), write to [email protected] and we'll answer directly.
We store your context. We never store warehouse credentials.