One front door between your AI clients and your apps

Connect your AI clients to approved apps through one gateway. Set policies for what agents can do, what data they can receive, and how requests are handled.

Free Trial

Your teams

  • Sales
  • Engineering
  • Support

AI clients

  • Claude
  • Claude Code
  • Cursor
  • Codex

Dtwo

  • Single sign-on
  • Expressive policies
  • Sensitive data redaction
  • Dynamic safeguards
  • Audit log

Your apps

  • Sales
    • Salesforce
    • HubSpot
    • Outlook
    • Microsoft Teams
  • Engineering
    • GitHub
    • Jira
    • Datadog
    • Your own MCP server
  • Support
    • Zendesk
    • Confluence
    • SharePoint
    • Slack

Stop managing AI connections one laptop at a time

When people connect AI clients to work apps individually, connections and permissions become harder to manage. Dtwo gives supported AI clients a shared route to approved apps, with policies and visibility built in.

Without Dtwo

  • Connections managed separately
  • Permissions spread across clients and apps
  • No shared view of gateway activity

With Dtwo

  • Approved connections through one gateway
  • Policies applied to tool requests
  • Gateway activity and decisions in one place

What happens on every request

Every time AI uses an app, Dtwo checks what it asks for and what comes back.

  1. 1
    AI client

    AI wants to do something

    “Send this file to…”

  2. 2
    Dtwo

    Who's asking?

    Signed in through your identity provider

  3. 3
    Dtwo

    Is this allowed?

    Expressive policies allow or block it

  4. 4
    Your app

    App does the work

    As that person, with their access

  5. 5
    Dtwo

    What's coming back?

    Sensitive data is masked

  6. 6
    AI client

    AI gets a safe answer

    And it's all in the audit log

Blocked at step 3

Claude tries to email a customer list to a personal Gmail address

send_mail → to: alex@gmail.com

attachment: customers_q3.xlsx

Blocked: outside recipients not allowed

Masked at step 5

Cursor reads a support ticket that includes a card number

“Customer says card [REDACTED] was charged twice on Oct 12…”

Answered. The card number never reached the model

Set it up once

Connect once, set the rules, and it works in every AI client

  1. Connect your apps once

    Add the MCP servers you already use, from vendors like Microsoft, Salesforce and HubSpot or ones you built yourself.

  2. Decide what AI is allowed to do

    Let AI read the CRM but not delete records. Let it draft emails but not send them outside the company. Start from ready-made bundles in the policy catalog or write custom policies in plain English.

  3. Connect Dtwo to your team's AI clients

    Add one Dtwo URL to Claude, Claude Code, Cursor, Codex or any AI client that supports MCP. People sign in once and get every app you've approved, with your rules already in place.

Run it your way

Hosted by Dtwo

Use Dtwo's hosted gateway. Set up approved connections and manage policies through the Dtwo console without running the gateway infrastructure yourself.

  • Easy to set up. Sign up and start connecting apps right away. No installs, no servers to provision.
  • No infrastructure to manage. No upgrades or on-call. We keep it running.

Good for teams that want to get going fast and don't have strict rules about where their data is processed.

Self-hosted

Run the Dtwo gateway in your own infrastructure, with control over the deployment environment. See the deployment documentation for prerequisites and data handling.

  • Maximum control. You decide where it runs, how it's set up and who can reach it.
  • Your data doesn't leave your infrastructure. It stays inside your walls.

Good for regulated industries like healthcare and finance, and companies with strict security or data residency requirements.

Close the side doors

Make Dtwo the approved way your AI clients connect

Employees can connect AI clients to company apps through unapproved MCP servers, creating activity outside your security team's visibility.

For supported managed AI clients, admins can restrict unapproved MCP connections and configure Dtwo as the approved gateway. Requests routed through Dtwo are checked against your policies.

MCP connections

  • Dtwo Allow
  • Other connections Off
Every AI client is set to connect only to Dtwo. There's no way around your policies.
Full setup guide in the docs

FAQs

What is an MCP gateway?

MCP is how AI clients connect to apps like your email, CRM or code repos. A gateway sits between the two, so every connection goes through one place where you set the rules and see what's happening.

What changes for people in the AI clients they already use?

Very little. They keep using Claude, Cursor or Codex. Instead of setting up each app themselves, they connect to Dtwo once and get every app you've approved.

Do people still handle their own API keys and tokens?

No. People sign in with your identity provider, like Microsoft Entra or Okta. Apps that use sign-in see the real person, so their existing permissions apply.

Can we put our own MCP servers behind it?

Yes. Add your internal MCP servers next to vendor ones. They get the same sign-in, policies and audit log.

What kinds of policies can I set?

Allow or block specific actions, block them only in certain cases (like sending outside your domain), mask sensitive data in responses, and dynamic safeguards that react to what's already happened in a session. Start with ready-made bundles from the policy catalog or author custom policies in plain language.

Can people get around it?

No. In each AI client's admin settings, you allow only Dtwo and turn off custom connections. That makes Dtwo the only path to your apps.

Where does Dtwo run, and is my data stored?

Dtwo can be hosted by us or run on your own infrastructure. It checks requests and responses as they pass through so it can apply your rules. Dtwo only stores metadata about each tool call, like who made it and what the policy decision was. The data sent to the tool is never stored.

How long does a rollout take?

You can go from signup to policies enforced in about 15 minutes. We've had customers sign up on a Wednesday and have Dtwo rolled out to their whole organization by Friday.

Your workforce is already using AI. Dtwo makes sure they're using yours.

Make the sanctioned path the easiest one, and see every connection it makes.

Free Trial
Get in touch

Tell us what you need to govern.

A few lines is plenty — what you're deploying, and what you need control over. We read every one.