- Scenarios where alternatives are better
- If you need a decades-mature, highly standardized ERP finance/HR/payroll suite with a large ecosystem, established vendors such as Tyler are more proven as a core transaction backbone.
- If you need deep, end-to-end permitting/licensing with extensive prebuilt code-enforcement workflows, a permitting-focused platform such as Accela generally provides greater domain coverage.
- If procurement requires widely recognized third-party security attestations and detailed public security documentation available immediately, larger vendors may have more readily available SOC/ISO artifacts and standardized security packets.
- If the organization cannot support iterative delivery and requires a fixed-scope, fixed-requirements implementation model, the vendor’s described phased approach may be a poor fit.
- If the buying organization requires abundant peer reviews and community knowledge to de-risk the purchase, FSH currently has a limited accessible footprint on G2/TrustRadius/Gartner Peer Insights.
- Red flags to watch in the buying process
- Inability to provide a security package (SOC reports, pen test summary, incident response plan) under NDA.
- Lack of a clear data ownership/export plan and public records retention alignment.
- Vague AI claims without clear model governance, audit logs, or explainability where required.
- Current limitations acknowledged by the vendor
- Terms of Service acknowledge service interruptions may occur and that SLAs are defined in individual contracts.
- Features on the roadmap (not yet available)
- Press coverage suggests expansion ambitions into additional public safety/operations domains, but public roadmap dates are not clearly documented in captured sources.
- Scale limitations
- No public stress or scale benchmarks were found.
- Security or compliance gaps
- Security certifications (SOC 2/ISO) are not publicly documented.
- AI model governance details (training data boundaries, auditability, human override) are not described in public documentation captured for this research.
- API limitations or integration constraints
- No public API documentation was found in the captured sources; integration claims exist but should be validated via technical diligence.