Integrations & Compatibility
Most agencies go live without any integration work. Here's what connects and what doesn't — and why some non-integrations are intentional by design.
Go Live Without Your IT Department
The biggest obstacle to deploying software in law enforcement isn't budget — it's IT approval timelines. Both products are designed so agencies can go live in 3 weeks without touching existing systems.
Officers type incident reference numbers manually. This is intentional — it keeps the system outside CJIS scope and eliminates months of IT integration work before you can start using it.
Stand-alone QR and barcode scanning. Works on any device with a camera — phone, tablet, or desktop webcam. No connection to existing armory software required to start tracking gear.
User accounts are managed within the application. A commander can set up a new user in minutes. No dependency on your department's AD or SSO infrastructure.
Cloud-hosted and accessible from any browser on any network, including officer mobile devices in the field. No VPN client to install or maintain.
API Access for Custom Integration
Both products expose a documented REST API for agencies that need to connect with existing systems. API documentation is provided during evaluation.
- Reporting and BI tools (PowerBI, Tableau) for command dashboards
- Existing agency data warehouse or export pipelines
- HMIS-compatible export format for OutreachLink (data can be mapped to HMIS schema on request)
- Custom agency portals or internal tooling
Full API documentation is provided to agencies during the evaluation process. Request access during your demo.
HMIS Compatibility
OutreachLink data can be mapped to HMIS schema on request, supporting HUD grant compliance reporting for programs such as ESG (Emergency Solutions Grants) and CoC (Continuum of Care).
What We Intentionally Don't Integrate With
Some non-integrations are not limitations — they are architectural decisions that keep both products outside CJIS compliance scope and protect agencies from a class of risk entirely.
Records management and computer-aided dispatch systems contain Criminal Justice Information. Integrating with them would pull CJI into OutreachLink and UnitGear — creating a CJIS compliance obligation for both products. The text reference field for incident numbers is the deliberate alternative.
Same reason. Any integration that introduces CJI into the system changes the compliance posture of the entire platform. This is a hard architectural boundary, not a feature gap.
This is the general rule. If an integration would cause Criminal Justice Information to flow into OutreachLink or UnitGear, it will not be built — regardless of customer request. This protects agencies as much as it protects M. Shores Tech.
Have an Integration Requirement?
Bring your specific requirement to the demo. We'll tell you what's possible, what's in scope, and what the timeline looks like — before you sign anything.