- When rapid adoption with minimal professional services is required
- A highly configurable investigative platform can require significant discovery, configuration, and integration work.
- When procurement requires public compliance artifacts early in the evaluation
- If the procurement process mandates publicly documented SOC 2 or ISO certification scope and currency before shortlisting, the lack of clear public documentation may slow evaluation.
- When the primary requirement is eDiscovery review at scale rather than investigative case workflows
- eDiscovery-first platforms (for example, Nuix Discover, Exterro, Relativity ecosystem) may be a better fit depending on data sources, legal-hold defensibility, and review workflows.
- When transparent, self-serve SaaS pricing is a priority
- Vendors with clear public pricing (for example, Kaseware) may reduce friction for early-stage evaluation.
- Current limitations acknowledged by the vendor
- Public-facing documentation focuses on capabilities; specific limitations, scale constraints, or detailed roadmap items are not prominently published.
- Roadmap (not yet available)
- A public, date-specific roadmap is not published on xanalys.org.
- Scale limitations
- The vendor states scalability for large and complex cases, but independent benchmarking and published scalability metrics are not publicly available.
- Security or compliance gaps
- Public documentation gaps exist for published certifications and detailed control descriptions. Procurement teams should request:
- SOC 2 Type II report (if available)
- ISO 27001 certificate (if applicable), scope statement, and validity dates
- Penetration-testing summaries and a vulnerability management overview
- Data residency and hosting architecture documentation
- API limitations or integration constraints
- Integration and API details are not publicly documented in full; these should be validated during technical workshops.