Security & Identity · Integration
DuoCircle
Add DuoCircle to your product for your customers, and give your AI agents governed access to it.
Embed a DuoCircle integration so your customers can manage their own email security setup from inside your product, working the domains, users, and settings on their own account. Each customer grants access to their own account, permissions are scoped per tenant, and every call is recorded so a configuration change can be traced back to its source. fastn handles each customer's credentials and API upkeep, so onboarding a new account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own protected domains and user configuration into your product.
Add or update a domain or user from your product as part of a governed onboarding workflow.
Surface delivery and protection status so your users do not need a second admin console.
Trigger your product when a configuration or protection status changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a customer's current domain and user configuration before recommending a change.
An agent applies a configuration change within governed, least-privilege permissions.
An agent reacts to a status change and notifies the owner who needs to act on it.
Example prompt
List protected domains for this customer and flag any whose configuration differs from our recommended baseline.
Set up DuoCircle in 4 steps
- 01Open the DuoCircle connector from your fastn dashboard.
- 02Have each customer authenticate their DuoCircle account with least-privilege credentials.
- 03Map the domains, users, and settings your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the DuoCircle integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DuoCircle integration without building it. Your customers connect their own DuoCircle account inside your product and work their users, groups and roles there, with no per-customer code on your side.
- Handle the part that actually costs time: the blast radius of an error is large, so least-privilege and auditability are non-negotiable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a DuoCircle update is not your on-call problem.
- One integration serves your product and your agents. The same governed DuoCircle connection powers in-product features and gives AI agents scoped, audited access, so you keep access and identity in step across a customer's estate without wiring it twice.
Used by these teams
Compare with
Okta
Duo SecurityWorks well with
ServiceNowOften used alongside
Tools the same teams tend to run next to DuoCircle, across other categories.
Datadog
PagerDuty
AWS CloudWatchDuoCircle integration FAQ
How do I add a DuoCircle integration to my product?
Enable the DuoCircle connector in your fastn dashboard, then let each customer authenticate their own DuoCircle account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DuoCircle client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DuoCircle account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DuoCircle account and only ever sees their own users, groups and roles. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this DuoCircle integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a customer's current domain and user configuration before recommending a change.
Who maintains the DuoCircle integration?
fastn does. When DuoCircle changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
What permissions does the DuoCircle integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own DuoCircle tenant, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source.
Can access changes be automated safely?
Yes. Provisioning and deprovisioning can be driven from your product or an agent within governed permissions, with every action audited, which is what makes automated access changes reviewable after the fact.
What can I build with the DuoCircle integration?
A common starting point: read their own protected domains and user configuration into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the DuoCircle integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DuoCircle does not change your per-connector cost. You can start free with 3 connected accounts.
Add DuoCircle to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.