Deploy Durin. Put agents to work.
Start with one workflow. Connect your systems, decide what agents can change and prove the controls before expanding.
Your agents. One governed path.
Durin is hosted. Your team configures the workspace, connections and policies.
Your Agent Clients
Claude Code · Codex · Cursor
Durin Hosted Gateway
Identity → Policy → Approval → Audit
Your Connected Systems
GitHub · Slack · Notion · MCP
Direct API calls, browser actions and shell commands that bypass Durin need separate controls. Private MCP servers need supported connectivity or an approved bridge.
Your first rollout, step by step.
An example schedule for one workflow. Agree dates around your identity, provider and security requirements; advance when the checks pass.
Days 1–3
Choose the work. Set the rules.
IT Operator + Security Lead- Pick one workflow, its systems and the people who own them.
- Create your workspace and assign administrators. Configure SSO and directory sync if your organization has Enterprise.
- Publish access policies and name independent reviewers before enabling production changes.
Set Up Your WorkspaceReady to Advance
An agreed workflow, bounded access and a published policy.
Week 1
Connect one system. One team.
IT Operator + System Owner- Add a provider, complete its authorization and review the tools and resource permissions.
- Pass the read-only readiness test, review billing and enable the connection.
- Connect the intended agent client to its personal Durin endpoint and complete MCP authorization.
Add Your First ConnectionReady to Advance
The intended member can run a reviewed read through Durin.
Weeks 2–3
Prove the controls. Then allow changes.
Security Lead + Technical Lead- Test allowed and denied resources, tool changes, independent approval, expiry and uncertain outcomes against your actual setup.
- Run a scoped change. Inspect the decision and execution outcome, and confirm revocation stops access.
Run the Evaluation KitReady to Advance
Recorded results for the pilot, with a clear go / no-go decision.
Week 4 onward
Expand the rollout. Keep ownership.
IT Operator + Technical Lead- Add teams and connections in batches. Repeat authorization, tool review and verification for each system.
- Enroll devices for Shadow MCP discovery. Review reported endpoints alongside sessions and audit records.
- Assign ongoing owners for approvals, access revocation, retention and incident response.
Find Reported MCP ConnectionsReady to Advance
Each new workflow has an owner and the same verified controls.
One rollout. Clear ownership.
- IT Operator
- Configure identity, connections and clients. Own day-to-day access and support.
- Security Lead / CISO
- Approve policy, review test evidence and set escalation and retention requirements.
- Technical Lead / CTO
- Choose the workflow, confirm the integration path and decide when to expand.
Bring the 90-day program into your rollout.
Scope and price are agreed before the program starts. Connections are billed separately.
For guided delivery, add the AI Governance Program: map AI use, develop policies, enforce controls and prepare framework evidence. Our team does the setup. Your team makes the decisions.
Explore the 90-Day Program