- If you need abundant third-party reviews and public benchmarks
- If internal stakeholders require Gartner/G2/TrustRadius evidence as a gating factor, FARA may be harder to justify due to limited accessible review footprint.
- If your procurement mandates specific public security certifications
- If procurement requires publicly verifiable SOC 2 Type II or ISO 27001 certification pages, the lack of public documentation is a risk until clarified.
- If you need a lightweight, single-purpose component
- Some agencies prefer best-of-breed (e.g., separate specialist vendors for validators, RTI, and passenger-facing apps). In such cases, FARA’s integrated suite may be less compelling than focused alternatives.
- If you cannot tolerate vendor dependency risk in fare collection
- Account-based fare collection is mission critical; agencies should evaluate resilience, DR, and operational governance carefully. If FARA cannot meet strict operational requirements (SLAs, multi-region failover, clear RACI), larger incumbents may be preferred.
- Publicly observable limitations (from sources reviewed)
- Limited public detail on:
- Security posture (certifications, encryption specifics, IAM model)
- Data residency
- Public pricing
- Third-party user satisfaction metrics
- Roadmap / future features
- Vendor communications discuss industry direction (ABT, interoperability, reducing payment friction), but do not provide a concrete, dated roadmap in the accessible pages reviewed.
- Scale limitations
- No public throughput, latency, or validator performance benchmarks found in sources reviewed. Buyers should request:
- Tap/validation throughput per door
- Offline mode behavior
- Settlement and reconciliation performance
- DR targets (RPO/RTO)