The connectors we stand behind today— and the ones we’re scoping next.
Curtainwall layers patch triage and named-human escalation on top of the endpoint source-of-truth you already run — never a forklift. Four EDR connectors are live today; identity and SaaS admin consoles are scoped for the next quarter. Don’t see yours? Request it; a real person reads everything that lands in the integration inbox.
EDR connectors enrolled customers are running right now.
Each connector is a read-only device sync — your EDR stays the source of truth for detection; we layer the patch queue, named-human escalation, and the audit log on top. No agent swap, no port forwarding.
- Live todayCrowdStrike FalconEndpoint security
Read-only device sync out of Falcon — CrowdStrike stays the source of truth for detection, we layer patch triage and named-human escalation on top.
- Live todaySentinelOne SingularityEndpoint security
Pull Singularity endpoints into the same autodiscovery loop; per-region token supported, no agent swap.
- Live todayDatto EDREndpoint security
For MSPs running SIRIS / Autotask — Datto is the device inventory of record and we curate the patching and triage queues against it.
- Live todayMicrosoft Defender for EndpointEndpoint security
For Windows-heavy orgs — Defender stays the source of truth for detection via Microsoft Graph, and we layer the same patch triage and named-human escalation on top.
Adjacent categories on the engineering roadmap.
These are the lanes the integrations team is scoping for the next two quarters. If one of them is the reason you’d evaluate us, request it — we prioritise the inbox that has the most real buyers behind it.
- Coming soonIdentity providersIdentity
Okta, Entra ID, and Google Workspace — bring SSO users into the same escalation context so the technician knows who is logged in, not just which endpoint.
- Coming soonSaaS admin consolesSaaS ops
Workspace and Microsoft 365 admin layers, scoped read-only — the same audit-log story for the cloud suite that we already run for endpoints.
Request the integration, then enroll the fleet.
Submissions are pre-tagged for the integrations lane and triaged alongside the main contact inbox. We’ll write back from the same address — usually within one business day.