Reaches What You Already Run.
Every system below is reached one of three ways: an API with tool-level allow and deny, a binding Ariad builds from the vendor's documentation, or a governed Workspace for a console with no API. Models sit behind the gateway, not in the list. Nothing is connected until a plan review grants it, tool by tool, per agent, per outcome.
A Connector List Ends Where the APIs End. Ariad Does Not.
A connector list reaches only what someone has already built a connector for. Ariad reaches a system through its API, through its documentation, or through its console when there is no API at all, including the mainframe. Whichever door, the same contract bounds the agent and the same record captures every call.
Each card below is one door. Select it to filter the catalog to the systems reached that way; the category pills narrow it further.
Tags: Connector is reached through its API with tool-level allow and deny. By design is reached through a binding built from documentation, a governed Workspace, or the model gateway. No system is connected until a plan review grants it, tool by tool.
Cloud and infrastructure
accounts, consoles, infrastructure as codeSource control and delivery
repositories, pull requests, pipelines, artifactsMonitoring, ITSM and support
alerts, incidents, tickets, change recordsData and analytics
warehouses, databases, pipelines, BIDocuments, knowledge and collaboration
wikis, document stores, work management, meetingsCRM, sales and service
customers, pipeline, cases, contractsERP, finance and procurement
ledgers, spend, close, planning, paymentsHR and talent
people, payroll, hiring, learningGovernance, risk, legal and security
controls, audit, contracts, discovery, security platformsCommunication
email, chat, voice, SMSIdentity
your identity provider; agents federate here, nothing is granted by defaultCore systems with no API
mainframes, appliances, virtual desktops, homegrown toolsModels, through the gateway
approved models on your keys; not integrationsIt still has a door.
If it has documentation, Ariad builds the binding scoped to the outcome. If it only has a console, a governed Workspace drives it. Ask, and we will tag it.
In Your Words.
Is this the list of what is installed?
No. It is the working catalog of systems Ariad can reach, each tagged with how. A system reaches a plan only when your administrator grants the specific tools an agent may call.
A system we run is not listed. Does that end it?
No. If it has documentation, Ariad builds the binding scoped to the outcome. If it only has a console, a governed Workspace drives it. Ask, and we will tag it.
Why are identity providers listed separately?
Because they are not integrations. Agents get their identities there, and nothing is granted until you grant it.