Integrations

If your users log into it, we can protect and govern it

Four integration paths cover the whole estate: standard federation protocols, a Python connector framework for anything with an interface, browser-plugin SSO for legacy logins, and ticketing workflows for systems without APIs.

Directories & identity sources

Authoritative sources that drive authentication and lifecycle events.

  • Microsoft Active Directory
  • Microsoft Entra ID (Azure AD)
  • OpenLDAP
  • Google Workspace Directory
  • HRMS platforms (via connector framework)
  • Databases & CSV/API feeds

Business applications

SSO via SAML/OIDC/OAuth2 and provisioning via connectors.

  • Microsoft 365
  • Google Workspace
  • Salesforce
  • SAP applications
  • Zoho suite
  • Tally & finance systems
  • Atlassian (Jira, Confluence)
  • Custom web applications

Infrastructure & network

Authentication for the layers beneath your applications.

  • VPN gateways (RADIUS MFA)
  • Network devices (RADIUS)
  • Linux servers
  • Windows servers
  • Apache Guacamole
  • Cloud consoles (AWS, Azure, GCP)

ITSM & ticketing

Provisioning workflows for applications without APIs, and request integration.

  • ServiceNow
  • Jira Service Management
  • Zoho Desk
  • Custom ITSM (via connector framework)

Legacy applications

Browser-plugin SSO with credential auto-fill and automatic rotation.

  • Legacy web applications (any login form)
  • Core business systems without federation
  • Vendor portals
  • Intranet applications

Don't see your application? That's normal — this list shows common targets, not limits. The Python connector framework plus browser-plugin SSO means coverage is a scoping conversation, not a product limitation. Ask us about your specific estate →

Bring us your integration list

Send your application inventory and we'll map each system to its integration path — federation, connector, plugin or ticketing — before you commit to anything.