Supported integrations

The integrations in this table are to systems running inside your own network, and that is the deployment the product is designed around. The wider system catalog also lists systems that exist only as a cloud service; a row that cannot serve a disconnected deployment says so and says why, and on a disconnected network such a system is simply never configured.

System	For	Direction
SQL Server	Application data and inventory sources	Read/write and read-only
Corporate directory (LDAP)	Contact search, group checks	Read
SMTP	Calendar invitations and email	Write
OIDC	Single sign-on	Read
SMS gateway	Reminder to the system owner	Write
Ticketing system (SOAP)	Open and update a ticket	Write
Database inventory (Oracle)	Database list and ownership	Read
Dependency monitoring	The host-to-host connection map	Read
Network device management	Non-server equipment	Read

Two rules that apply to all of them

An integration failure does not fail the action. A ticket that could not be opened does not cancel the window — it is recorded and shown. The opposite behaviour, where a secondary service failing cancels an action the user already confirmed, is worse.

Every integration can be switched off. An organisation without an SMS gateway or without a ticketing system uses the product without them, and does not see an interface pointing at a service that does not exist.

[VERIFY] — the exact supported versions of each product are agreed with the deployment team and depend on the environment.