durin
Book A Demo
Knowledge base
Getting started

What is Durin?

Understand where Durin sits between an AI client and your company tools.

Everyone1 min read

The governed request path

Durin provides MCP Governance. Your AI client sends a tool request to Durin, which checks the requesting identity and access rules before sending an allowed request to the provider.

  1. A person authenticates their client using their own Durin endpoint.
  2. Durin checks membership, connection access, reviewed tools, resources, credentials, and policy.
  3. An allowed request reaches the provider. Activity records the decision and execution outcome.

What MCP Governance covers

Durin governs requests routed through it. Your team must separately manage direct provider access, other client endpoints, and any network controls needed for its rollout.

Frequently asked questions

Does Durin host my AI model?

No. Your AI client uses its configured model. Durin governs the tool requests sent through its gateway.

Does an allowed decision mean the request succeeded?

No. Authorization and provider execution are separate. Check the execution outcome in activity.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.