- Organizational scenarios where the product may be inappropriate
- Very small agencies seeking lightweight, low-cost, cloud-first tools may find a full CAD/RMS/JMS suite disproportionate to their needs and budgets.
- Industries or use cases where alternatives may be preferable
- Agencies required to use state-standard platforms or vendors mandated by state procurement rules should follow those directives and may not be able to select this product.
- Technical requirements that may preclude selection
- If pre-qualification requires published SOC 2 Type II and/or ISO 27001 certifications and the vendor cannot provide them under NDA, this could be a hard stop.
- Budget constraints
- Agencies that cannot fund implementation services, interfaces, and training should consider lower-cost or more narrowly scoped products.
- Specific workflows or integrations to validate
- Agencies that require prebuilt integrations to specific state systems (e.g., state courts, e-citation systems, state RMS hubs, local GIS, jail medical systems) should validate whether the vendor has existing deployed integrations; otherwise, expect custom work.
- Red flags to confirm during procurement
- The vendor cannot provide:
- A CJIS Security Addendum-aligned security package.
- A clear RACI for patching, incident response, and audit support.
- Multiple comparable references that align with agency size and call volume.
- Limitations disclosed by the vendor
- The vendor site does not include a public list of known issues or a dated public roadmap in the reviewed materials.
- Roadmap and feature availability
- No public roadmap with target dates was found in reviewed sources.
- Scale limitations
- The vendor does not publish scale limits in the reviewed materials; buyers should request performance and scale validation aligned to their expected call volumes and data volumes.
- Security or compliance gaps
- The primary observable gap is the lack of publicly documented SOC 2/ISO certifications and the absence of public pen test summaries or whitepapers. The vendor describes CJIS alignment for RMS features, but CJIS compliance should be validated through architecture review and contractual commitments (https://www.goeis.net/rms, https://www.fbi.gov/file-repository/cjis).
- Technical debt and architecture notes
- No independent review corpus was found to assess technical debt. Buyers should request architecture documentation, reference architectures for hosted deployments, and upgrade/migration practices.
- API and integration constraints
- Public API documentation was not located in the reviewed materials. Buyers should request API documentation, sample integrations, and a list of previously completed integrations.