Softwr

Cybersecurity · head to head

IBM QRadar vs ThetaRay

IBM QRadar logo

IBM QRadar

Cybersecurity

Enterprise SIEM licensed by events per second, whose cloud business IBM sold to Palo Alto Networks in 2024.

From
On request
Rated
-
Full reviewWebsite
ThetaRay logo

ThetaRay

Cybersecurity

Unsupervised AI transaction monitoring for cross-border and correspondent banking

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: IBM QRadar iBM sold the QRadar SaaS business to Palo Alto Networks in 2024 and those customers are being moved to Cortex XSIAM, so anyone buying today is choosing an on-premises product whose vendor has publicly moved the cloud future to a competitor, and the support horizon becomes a contract negotiation rather than an assumption.; ThetaRay unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • They diverge on capability: IBM QRadar covers Offence model, ThetaRay covers Unsupervised detection.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which IBM QRadar and ThetaRay actually diverge.

Attributes where IBM QRadar and ThetaRay differ
AttributeIBM QRadarThetaRay
Pricing modelsubscriptionquote
PlatformsWeb, ApiWeb
Founded1911Unknown

Identical on both: starting price (On request), free tier (No), user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in IBM QRadar

  • Offence model
  • Network flow analysis
  • Device Support Modules
  • Ariel query language
  • Rules and building blocks
  • Deployment topology
  • App Exchange
  • Use Case Manager

Only in ThetaRay

  • Unsupervised detection
  • Cross-border focus
  • Sanctions screening
  • Alert triage
  • Customer risk scoring
  • Cloud native

What people use each for

The jobs each tool is most often brought in to do.

IBM QRadar

  • A regulated enterprise that must keep log data on premises or in a specific jurisdiction and cannot use a shared SaaS SIEMnot ThetaRay
  • A SOC that wants log correlation and network flow analysis in one platform rather than buying an NDR product separatelynot ThetaRay
  • An existing QRadar estate deciding whether to stay on premises or accept the migration path to a different vendor's platformnot ThetaRay
  • Compliance-driven log retention and reporting where the audit requirement is specific about collection, retention and reportingnot ThetaRay

ThetaRay

  • A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot IBM QRadar
  • A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot IBM QRadar
  • A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot IBM QRadar
  • A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot IBM QRadar

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

IBM QRadar

  • IBM sold the QRadar SaaS business to Palo Alto Networks in 2024 and those customers are being moved to Cortex XSIAM, so anyone buying today is choosing an on-premises product whose vendor has publicly moved the cloud future to a competitor, and the support horizon becomes a contract negotiation rather than an assumption.
  • Licensing is by events per second and flows per minute, so every additional log source raises the cost directly and teams routinely exclude verbose sources such as DNS, proxy, endpoint and cloud audit logs to stay under the licence, which strips out exactly the data an investigation later needs.
  • It needs a dedicated operator: rule tuning, parser work and offence triage are continuous jobs, and an organisation that deploys QRadar without at least one named engineer accumulates thousands of unreviewed offences and a false sense of coverage.
  • A log source without a matching Device Support Module arrives unparsed, and writing a custom parser with regular expressions against an unfamiliar payload format is specialist work that can take days per source, which quietly determines which systems ever get monitored.
  • On-premises capacity is planned across consoles, processors, collectors and data nodes, so outgrowing the sizing means procuring and racking more appliances rather than changing a subscription tier, and growth becomes a purchasing cycle measured in months.

ThetaRay

  • Unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • The alert reduction claim depends heavily on your data, so a parallel run is essential and adds months and cost before you can decommission the incumbent.
  • Coverage is strongest in cross-border and correspondent flows; institutions whose risk is domestic retail fraud will find the fit weaker than a general-purpose monitoring platform.
  • It is a smaller vendor than the incumbents, so integration connectors into legacy core banking systems are often bespoke work rather than a supported adapter.
  • Model retraining and tuning are vendor-led, which means changing detection behaviour is a support conversation rather than something your own analysts can do that afternoon.

Pricing, plan by plan

IBM QRadar

On request
  • QRadar SIEMFree
    • Event and flow processing
    • Offense management
    • Threat intelligence
  • QRadar CloudFree
    • Cloud-native deployment
    • Elastic scaling
    • Managed infrastructure
  • QRadar SuiteFree
    • SIEM + SOAR + XDR
    • Unified analyst experience
    • Federated search

ThetaRay

On request
  • ThetaRay Sonar$undefined/year
    • Priced by monitored transaction volume and number of monitored entities
    • SaaS on Azure with regional data residency options
    • Parallel run and model tuning included in onboarding

Which should you pick?

Choose IBM QRadar if

  • You need offence model.
  • You work on Web, Api.
  • You also want network flow analysis.
IBM QRadar review

Choose ThetaRay if

  • You need unsupervised detection.
  • You also want cross-border focus.
ThetaRay review

Questions people ask

Is IBM QRadar or ThetaRay better?
Neither clearly leads. IBM QRadar starts at On request and ThetaRay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, IBM QRadar or ThetaRay?
IBM QRadar starts at On request and ThetaRay at On request.
Does IBM QRadar or ThetaRay run on more platforms?
IBM QRadar runs on Web, Api. ThetaRay runs on Web.
What is IBM QRadar best used for?
IBM QRadar is most often used for a regulated enterprise that must keep log data on premises or in a specific jurisdiction and cannot use a shared saas siem, a soc that wants log correlation and network flow analysis in one platform rather than buying an ndr product separately, an existing qradar estate deciding whether to stay on premises or accept the migration path to a different vendor's platform, compliance-driven log retention and reporting where the audit requirement is specific about collection, retention and reporting. Of those, a regulated enterprise that must keep log data on premises or in a specific jurisdiction and cannot use a shared saas siem and a soc that wants log correlation and network flow analysis in one platform rather than buying an ndr product separately are not what ThetaRay is typically brought in for.
What can IBM QRadar do that ThetaRay cannot?
IBM QRadar covers Offence model, Network flow analysis, Device Support Modules, Ariel query language. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.

Answered from the vendors’ own pages

IBM QRadar: Who owns QRadar now?

It is split. IBM sold the QRadar SaaS assets to Palo Alto Networks in a deal announced in May 2024 and closed that September, and those customers are being migrated to Cortex XSIAM. IBM retains and supports the on-premises product.

ThetaRay: Does it replace a rules engine entirely?

Rarely on day one. Most institutions run it alongside existing rules during a parallel period, and some keep specific regulator-mandated rules permanently.

IBM QRadar: Is QRadar being discontinued?

IBM has committed to continuing support for on-premises customers, including security updates, while offering migration assistance. The cloud product's future belongs to Palo Alto. If you are signing a multi-year term, get the support horizon written into the contract.

ThetaRay: Where is the data processed?

SaaS runs on Microsoft Azure with regional deployment options, which is the mechanism for meeting data residency conditions in regulated markets.

IBM QRadar: How is it licensed?

By events per second for logs and flows per minute for network data, with the software or appliance sized to that rate. Add-on modules in the suite are licensed separately.

ThetaRay: Is sanctions screening included?

Screening is available on the same platform but licensed as part of the commercial package rather than bundled by default. Confirm it is in your quote.

IBM QRadar: What is an offence?

QRadar's term for a correlated case. Rules group related events and flows against a common indicator such as a host or user, so an analyst reviews one offence rather than the hundreds of events behind it.

IBM QRadar: Do I need a full-time engineer?

In practice yes for anything beyond a small deployment. Parser development, rule tuning and offence triage do not stop, and the most common failure mode is a well-installed QRadar that nobody has tuned since go-live.

Share

Related pages

More on IBM QRadar

More on ThetaRay

Keep looking

Other head to heads