What is Durin?

When to use Durin

Use Durin when people and AI clients need a shared, reviewable way to reach company tools. Instead of giving every client an unrelated set of provider credentials and permissions, an administrator defines connections in Durin and each person connects through their own endpoint.

A typical rollout begins with one provider, one reviewed read tool, and a small group of users. This lets you confirm whose identity reaches the provider, which resources are available, and where to inspect the outcome before expanding access. You can explore the decision flow in the public MCP simulator without connecting a company system.

The governed request path

When an AI agent asks to use a tool — create a Jira ticket, read a GitHub repo, post a Slack message — Durin intercepts the request. It checks who is asking, what they are allowed to do, and whether the action needs approval before it reaches the upstream system.

Key concepts

Durin organizes access around a few core ideas: connections define which upstream systems are available, policies define what actions are allowed or require review, and the audit trail records every decision and its outcome.

Personal and admin workspaces

Every user has a personal workspace to manage their own connections, sessions, and activity. Administrators get a separate admin workspace with controls for people, teams, policies, approvals, billing, and organization-wide settings.

Follow one request from start to finish

Consider an employee asking an AI client to read a repository file. The client proposes a tool call; the proposal itself is not permission to read the file.

1. The employee connects the client to their personal Durin endpoint and authenticates as the same account.
2. Durin resolves the requested tool to a reviewed connection and checks current membership, team access, personal access, credentials, and the allowed resource.
3. If the checks permit the read, Durin dispatches it using the configured upstream authentication boundary.
4. The activity record lets you distinguish the access decision from the provider outcome. A permitted request can still fail upstream.

Know which responsibilities stay with your team

Durin governs requests that pass through its gateway. Adding a Durin endpoint does not remove other endpoints from a client, revoke provider credentials held elsewhere, or prove that every company request uses the managed path.

IT should confirm the client configuration and any network controls required for the rollout. Provider owners should review consent and resource scope. Administrators should establish who can change membership, approve requests, inspect evidence, and manage billing. Treat these as distinct responsibilities even when one person performs several of them.

Choose your next guide

If you are setting up a new workspace, start with the quickstart. If an administrator has already installed your tools, use the MCP client setup guide and connect with your own account. Administrators who need to understand installation states should read Understanding connections before enabling their first provider.