Claroty review

Claroty sells cybersecurity software for cyber-physical systems (CPS), including operational technology environments where connected equipment supports critical operations. The product brief describes the platform as AI-powered and focused on helping organizations identify risks, support compliance and keep operations running.

Its feature set covers several jobs: asset inventory for visibility into connected devices and their attributes; exposure management to identify and prioritize risks; network protection; secure access; and threat detection with alerts. The brief also says Claroty supports uptime and automates compliance reporting. Those are broad capabilities, not published guarantees about specific detection rates or uptime improvements.

For a buyer, the practical question is which Claroty product and architecture fit the environment. A Reddit discussion distinguishes the on-premises CTD product from cloud-based xDome and reports different sensor requirements. Claroty is therefore worth evaluating for CPS visibility, but buyers should confirm deployment details and pricing with sales before treating it as a like-for-like option.

Claroty’s stated coverage maps to several needs OT and CPS teams may have in one platform: knowing what is connected, identifying exposures, monitoring for threats and controlling secure access. The product brief also includes compliance reporting and operational efficiency, which may matter to teams trying to support uptime while documenting their security posture. The available material does not quantify those outcomes, so buyers should ask for evidence tied to their own environment.

There is at least one positive early comparison from users. In a Reddit thread about product evaluations, a participant who said they were a little over a week into trials of Claroty xDome and Dragos reported that xDome seemed to be doing a better job at asset identification. That is one user’s preliminary impression, not a controlled comparison or a broader performance finding.

The thread also includes a user who said they like xDome, while preferring Nozomi when strictly on-premises deployment is required. That suggests xDome may be the more compelling Claroty option for some cloud-oriented evaluations. Confirm the deployment model, asset coverage and required integrations in a proof of value rather than assuming the same fit across all CPS environments.

Price is the clearest purchasing unknown. The available pricing information lists a custom enterprise quote, with no published monthly or annual rate, starting price or included limits. It also does not publish a free-trial policy. The information is marked low confidence, so buyers should verify current terms with Claroty or a channel partner and request a quote that spells out what is included.

Architecture may complicate a switch. In one Reddit thread, a commenter reported that Claroty’s on-premises CTD and cloud xDome use different architectures and sensors, unlike the Nozomi setup they described. Another commenter said CTD was not competitive with xDome; that is an individual opinion, not an independent product assessment. Still, teams moving between deployment models should ask whether sensors, configuration or rollout work must change.

The published material gives no numerical caps for assets, users, sites, alerts or retention. Don’t assume those are unlimited: get the limits, add-on charges and renewal terms in writing before comparing Claroty with alternatives.

Claroty does not publish a list price in the published pricing information. The only listed option is a custom enterprise quote, with no monthly or annual figure. The published pricing page details do not identify a starting price, free plan, or free trial, so there is no public price to compare against a budget.

There is no published tier jump to calculate: the source lists no priced tiers. It also lists no add-ons, which does not confirm that every capability is included in a quote. Monthly and annual billing prices are not published, either. Pricing is described as negotiated through sales or channel partners, so ask for the quote in writing and confirm its term, billing schedule, included products, and any separate charges before comparing it with alternatives. The available information does not provide enough detail to estimate total cost. If predictable pricing is a requirement, treat that as a fit concern and get a quote before investing in evaluation.

The published material does not describe Claroty migration tools, deployment steps, data export formats, or the effort required to replace an existing platform. It also does not document how to remove Claroty or transfer asset and alert data elsewhere. Treat those as questions for the sales team, not as capabilities we can confirm from the available sources.

Architecture fit is a stated evaluation concern: our verdict advises confirming it before committing. Ask which components your environment needs, how existing asset inventories and workflows would be handled, and what data you can export if you leave. Get those answers in writing before signing.

We do not have Reddit posts or comments in the published material, so we cannot substantiate why users leave Claroty or make claims about support feedback. The available information flags that proven support feedback is lacking, but it does not establish a pattern of customer complaints. For a switch decision, ask for references from organizations with comparable CPS environments and clarify support terms in the quote.