Overview#
A regional law enforcement agency deploying the platform already runs Mark43 for records management, a Tyler Technologies CAD system, and a legacy jail management platform from a third vendor. Getting useful intelligence from those systems means getting their data into one place without writing custom integration code for each one. The Connector Registry solves that problem: 153 pre-built connectors cover the most common public safety, financial, social media, and government data sources, with schema discovery and field mapping that reduces integration setup from weeks to hours.
The platform features automatic schema discovery, smart field mapping, real-time data quality validation, and normalisation into standard schemas including NIBRS, UCR, NIEM, and GJXDM.
Key Features#
Pre-Built Connector Library#
153 connectors cover public safety and law enforcement systems including 40+ RMS platforms, CAD systems, jail management, and court records, as well as financial data sources, social media platforms, government databases, and commercial intelligence providers. Zero-configuration schema introspection with automatic field detection and type inference gets integrations running quickly.
Smart Field Mapping#
ML-powered field mapping suggestions based on semantic similarity and historical mapping patterns. Reduce integration setup time from weeks to hours by automatically suggesting how source fields map to destination schemas.
Real-Time Data Quality#
Field-level quality scoring with completeness, accuracy, consistency, and timeliness metrics. Monitor ingested data quality continuously and alert when data sources degrade or produce anomalous records.
Universal Normalisation#
Standardise disparate data formats into recognised schemas including NIBRS, UCR, NIEM, and GJXDM. Transform heterogeneous source data into consistent formats for cross-source analysis and reporting.
Bidirectional Sync#
Real-time bidirectional data synchronisation with conflict resolution and merge strategies. Connected systems stay in sync without manual data entry or batch transfer delays. Multi-tenant source isolation ensures polling configurations remain segregated between organisations.
Change Data Capture#
Incremental synchronisation with log-based change detection for minimal performance impact on source systems. Process only changes rather than full data refreshes, reducing load and latency.
Data Lineage and Provenance#
Complete lineage tracking from source system to analytics with transformation audit trails. Every data point carries a clear record of origin, transformation history, and last update time.
Use Cases#
- Multi-System Integration: Connect disparate public safety systems into a unified data platform for cross-system analysis and reporting without custom integration development.
- Data Migration: Migrate historical data from legacy systems with automated schema mapping, quality validation, and transformation into modern data standards.
- Intelligence Aggregation: Ingest and normalise data from multiple intelligence sources, commercial databases, and open-source feeds for comprehensive investigative support.
- Real-Time Data Sharing: Enable bidirectional sync between systems for inter-agency data sharing, regional information exchanges, and multi-jurisdictional collaboration.
Integration#
Supports connections to RMS, CAD, jail management, court systems, financial institutions, social media platforms, government databases, and commercial data providers. Standard authentication methods include API keys, OAuth, SFTP, and database connections. All ingested data writes go to the PostgreSQL primary data store.
Open Standards#
- OASIS STIX 2.1: Every connector must declare STIX 2.1 as its primary output contract when producing cyber-threat intelligence objects, ensuring interoperability with any STIX-compliant analysis platform.
- NIEM (National Information Exchange Model): Ingested records from RMS, CAD, and court systems are normalised to the NIEM information exchange model, enabling cross-agency sharing without bespoke transformations.
- OASIS CAP v1.2 (Common Alerting Protocol): Connectors ingesting emergency and public-safety alert feeds declare CAP 1.2 as their output contract, preserving the standard alert structure through the pipeline.
- STANAG 4607 (NATO GMTI): Ground moving target indicator feeds from military and border-surveillance sources are handled via the publicly available STANAG 4607 standard connector type.
- ITU-R M.1371 (AIS): Maritime vessel position and identity data is ingested using the Automatic Identification System standard, allowing interoperation with coast-guard and port-authority AIS feeds.
- OAuth 2.0 (RFC 6749): Connector authentication to external systems such as RMS and CAD platforms uses the OAuth 2.0 client-credentials flow, with API-key and bearer-token fallback where the upstream does not support OAuth.
- OpenAPI 3 / Swagger: Schema discovery automatically introspects connected REST APIs by fetching and parsing their OpenAPI or Swagger documents, removing the need for hand-authored field mappings.
- GraphQL: The entire connector registry management surface, including registration, heartbeat, health-check, and summary queries, is exposed through a typed GraphQL API.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14