Give each surface one job
Keep the website, application, management API, and MCP gateway distinct. Tenant, credential, job, mail, and provisioning work stays behind the authenticated operating boundary.
Ship agent integrations with governance built in.
Give platform teams a repeatable way to configure connections, review policy changes, preserve tenant boundaries, and move governed access toward production trust.
One governed path. Clear ownership at every step.
Keep product teams focused on the workflow. Durin provides the shared place to check identity, evaluate access, and record what happened.
Your agent clients
Approved MCP clients
Authenticated employees
Scoped workflows
durin
Identity · policy · approvals
Decision + execution evidenceYour company systems
Reviewed tools
Scoped credentials
Approved connections
Illustrative architecture. Governance applies to requests routed through Durin.
Create a clean handoff from setup to execution.
Keep configuration, connection review, policy, execution, and evidence legible as separate platform surfaces so teams can own the right part of the route.
Make change review part of the build
Keep connection drafts, tool mappings, policy versions, and schema changes explicit. Reviewers can see what will change before a connection moves toward activation.
Ship with a trust map
Track account permissions, tenant resources, identity, billing, email, private connectivity, client versions, retention, and recovery as separate checks with clear owners.
Start with a call you can explain.
Try a permitted read, an approval-required write, and revoked access. Then bring the same questions to your team’s first connection.
Make connection changes reviewable.
Create an account to manage connection onboarding, reviewed capabilities, policy changes, and uncertain writes.
Create an accountProduction connections use provider setup and trust review.