- Review platform summary (accessible sources)
- Gartner Peer Insights
- Rating shown: very highly rated with a modest review footprint (Data Loss Prevention market listing).
- Review excerpts available in the crawl are predominantly positive and comment on support and visibility.
- G2
- Rating shown: very highly rated with a small review footprint in the captured page crawl.
- The visible review excerpts are positive; cited cons are limited and often framed as minor or related to product maturity.
- TrustRadius
- No clearly accessible end-user review page for Reco was found in the searches performed; a TrustRadius-hosted Reco PDF product download exists, but PDFs are typically vendor-supplied collateral rather than verified end-user reviews.
- Direct quotes (positive)
- Gartner Peer Insights (example excerpt shown on Gartner page)
- "Reco has been excellent for several reasons, namely our customer support team… The tools that Reco provides have helped my organization gain visibility into areas that we would not have had otherwise."
- Gartner Peer Insights (review excerpt)
- "The team at Reco is attentive and passionate - we never feel as though we have to chase them for follow-ups…"
- G2 (Cloud Security Engineer)
- "We can even trust on Reco to be a source of truth, for alerts that we ship to our SIEM!"
- G2 (CISO)
- "Easy deployment… Intuitive dashboard… Great support…"
- Direct quotes (critical/negative or mixed)
- G2 (Security Engineer)
- "While Reco excels in visibility and automation, its potential limitations might include handling highly customized or niche SaaS applications with non-standard APIs… requires careful tuning to avoid excessive or inaccurate alerts."
- G2 (CISO)
- "Some minor features are yet to fully mature."
- G2 (CISO)
- "It’s an alarm, but doesn’t remediate - it’d be nice to have more remediations tied into the solution."
- Common criticisms and complaints (from accessible reviews)
- Limited native remediation actions (needs workflow/automation integration).
- Potential coverage gaps for niche/custom SaaS apps and API edge cases.
- Need for tuning to prevent noisy alerts (not heavily evidenced in the small visible sample, but explicitly mentioned in some reviews).
- Why customers chose this product over alternatives (what evidence suggests)
- Themes in reviews and vendor messaging include:
- Rapid deployment and quick time-to-value reported by reviewers and vendor materials
- Broad SaaS visibility (including shadow SaaS/AI as described by the vendor)
- Positive comments about support responsiveness
- Vendor emphasis on AI/agent governance features
- Why some customers left for competitors (churn reasons)
- No clear public churn narratives were found in the accessible sources; this is a gap. Buyers should request:
- Competitive bake-off results
- Reference calls including customers who evaluated multiple SSPM/SaaS security tools
- Specific outcomes customers achieved (with metrics when available)
- Vendor site claims (not independently verified): solution pages cite reductions in security incidents, faster incident response, improvement in compliance posture, and reductions in manual security tasks; methodologies are not provided.
- A vendor testimonial describes identifying redundant Smartsheet accounts and consolidating licenses, with an asserted cost saving.
- Vendor-published case studies identified
- Banco BS2 case study PDF (M&A context)
- Notes that initial visibility was substantial after implementing Reco, indicating broad discovery but also a change-management challenge.
- As vendor collateral, outcomes should be treated as directional; the methodology and counterfactual are not independently validated.
- SolarEdge case study PDF (SaaS security and productivity outcomes)
- Vendor framing indicates operational relief following deployment.
- As with most vendor case studies, baseline definitions and measurement methods are not fully disclosed.
- Critical evaluation (methodology gaps)
- Vendor case studies generally:
- Highlight successful deployments
- Lack independently audited ROI models
- Rarely include implementations that did not meet objectives
- Buyers should request:
- Reference customers with similar SaaS stacks and scale
- Evidence of false-positive rates, alert volumes, and how tuning was performed
- Examples of where Reco did not support an app and how the vendor addressed it (custom connector timeline, limitations)