Connects at the layer that matters, under your control.
Integrations are scoped, credentialed per organisation, and governed by the same entitlement model as the rest of the platform. Connecting a system does not widen anyone's access to it.
How to read this
Every entry carries a support state
These words mean specific things, and the counts are real. Several capabilities sit at 'not yet verified' — they are modelled in the platform but have never run against real hardware, and we would rather say so here than have you discover it during a trial.
- Available
- Works today once credentials are supplied.
- 7 capabilities
- Requires configuration
- Works today, and needs per-organisation setup — endpoints, credentials or network access.
- 7 capabilities
- Not yet verified
- Modelled in the platform, but never verified against real hardware. Do not plan a deployment around it yet.
- 2 capabilities
- Planned
- On the roadmap. Not built, and no date is committed.
- 6 capabilities
Integration catalog
Cameras & video
Virtik models cameras as first-class objects bound to real positions in a site. Live transport from third-party devices is the part that is not yet proven against hardware.
- Camera binding to the site modelPlacing a camera at its real position and field of view inside a Virtual Site, and resolving events to it.Available
- Camera inventory & commissioningRegistering devices, tracking commissioning state and recording what has been provisioned.Available
- ONVIF devicesDevice registration exists; the ONVIF transport client does not. A connection can be recorded but has never been verified against a real camera.Not yet verified
- RTSP streamsSame position as ONVIF: the stream can be registered, but no RTSP transport client exists yet.Not yet verified
- Video management systemsIngestion from an existing VMS rather than direct from devices.Planned
Mapping & spatial
The operational map and the site graph. The mapping provider token is set when the deployment is built.
- Vector basemap providerThe operational map used across Command Center and Live Operations. Requires an organisation mapping token.Requires configuration
- Device geolocationPositioning for personnel presence, from the field surface.Available
- Floor plans & 360° imagerySource material for authoring a navigable site model.Available
Identity & access
Who your people are and what they may do. Usually a precondition for an enterprise deployment.
- Email and password with MFABuilt-in authentication with multi-factor enrolment and AAL2 enforcement.Available
- Enterprise SSODomain-based SSO discovery and sign-in. Requires the identity provider to be configured for your organisation.Requires configuration
- Directory synchronisationKeeping personnel records aligned with your directory automatically.Planned
- Group to role mappingMapping directory groups onto Virtik operational roles.Planned
Communications
Reaching people outside the platform, with delivery tracked where the transport allows.
- SMSOutbound SMS with consent capture and STOP handling, plus an inbound webhook for replies.Available
- Mail provider connectionConnecting an organisation mailbox for operational correspondence, via the mail gateway.Requires configuration
- Push notification to devicesDelivery to enrolled mobile devices. No push service is deployed and no signing keys are configured, so nothing is deliverable today.Planned
- VoiceLive voice between operational participants. The state machine exists and reports honestly; no media transport provider is connected.Planned
APIs & webhooks
Personal access tokens and signed webhooks for integration events.
- Outbound webhooksSigned webhooks with retry and delivery tracking, backed by a real endpoint and delivery store. They deliver integration events today; incident and detection events are not delivered.Requires configuration
- Scoped API accessPersonal access tokens scoped per organisation, subject to the same entitlement model as a person. There is no general public REST API yet.Available
- Event stream exportBulk extraction of the operational event model for reporting and archival.Planned
Operational systems
Systems that are not security tools but participate in a security operation.
- Access control eventsDoor and credential events ingested as detection sources.Requires configuration
- Environmental sensorsSensor events ingested and resolved against the site model.Requires configuration
- Reporting & BI extractionFeeding operational data into external reporting tools.Requires configuration
Not sure whether your stack fits?
Connector availability varies by plan and deployment. The fastest answer is a technical session against your actual estate — what you run, what it speaks, and what would need configuring.
What is not on this page
- No vendor logos presented as partnerships.
- No integration whose support state is uncertain.
- No dates against planned work.
Each of these is absent because it is not verified, not because it is being withheld.