Enterprise: bring your own cloud

Renbase runs as a managed service, and it also runs inside your own infrastructure. For organizations whose corpus can't leave their perimeter — regulated industries, sensitive internal knowledge, strict data-residency requirements — BYOC is the deployment model: same product, your cloud, your keys.

What BYOC means here

The entire platform is deployed in an environment you own: the workspace, the API, the MCP endpoint for agents, and the storage where your documents and definitions live. Nothing about your corpus — content, questions, answers, usage — leaves your infrastructure.

It is the same product, not a reduced edition. Your team gets the workspace and its governance loop, your integrations get the API, and your agents get the MCP tools, exactly as documented in the rest of this site.

What's included

A BYOC engagement is guided, not a tarball and a wish of good luck:

• Deployment by our team. We install and configure the stack in your environment with your platform people, and leave it documented and reproducible.
• Onboarding with knowledge-management specialists. The hard part of a governed corpus isn't the software — it's deciding what goes in it. Our specialists work with your team to structure the initial corpus and glossary: which documents, which definitions, which rules, who approves what.
• A support and update arrangement sized with you. How updates are applied and what support looks like is agreed per engagement, depending on how much of the operation your team wants to own.

What we'll ask you

Requirements are sized together during scoping and depend on your corpus and traffic. Expect the conversation to cover where it will run (all major clouds work, as does on-premises), who on your side operates infrastructure, and how your people will sign in.

Starting the conversation

Write to [email protected] with a rough picture of your use case: the kind of content, roughly how many people and agents will ask, and any residency or compliance constraints we should design around. We'll come back with a scoping proposal.

If you're still evaluating, the comparison with managed RAG platforms explains where Renbase sits relative to the RAG services of the cloud you may already be using — BYOC is often the answer when the blocker is "our data can't go to another vendor".