Developer Tools · head to head
Cortex vs ThetaRay
Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No
ThetaRay
Cybersecurity
Unsupervised AI transaction monitoring for cross-border and correspondent banking
- From
- On request
- Free plan
- No
The short version
- Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; 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: Cortex covers Service catalogue, ThetaRay covers Unsupervised detection.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Cortex and ThetaRay actually diverge.
Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated).
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 Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
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.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot ThetaRay
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot ThetaRay
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot ThetaRay
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot ThetaRay
ThetaRay
- A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Cortex
- A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Cortex
- A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Cortex
- A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot Cortex
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.
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
Cortex
On request- Cortex$undefined/year
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
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 Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Questions people ask
- Is Cortex or ThetaRay better?
- Neither clearly leads. Cortex 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, Cortex or ThetaRay?
- Cortex starts at On request and ThetaRay at On request.
- Does Cortex or ThetaRay run on more platforms?
- Cortex runs on Web, API. ThetaRay runs on Web.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what ThetaRay is typically brought in for.
- What can Cortex do that ThetaRay cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.
Answered from the vendors’ own pages
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
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.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
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.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
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.
Cortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
Related pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs Earthly
- Cortex vs Spacelift
- Cortex vs Atlantis
- Cortex vs Depot
- Cortex vs Nix
- Cortex vs SonarQube
- Cortex vs Keycloak
- Cortex vs Ona (formerly Gitpod)
- Cortex vs Vite
- Cortex vs Bazel
- Cortex vs Dagger
- Cortex vs Deep Code
- Cortex vs Deno
- Cortex vs Fig
- Cortex vs Frappe
- Cortex vs Git
- Cortex vs Feedzai
- Cortex vs Unit21
- Cortex vs Quantexa
- Cortex vs Silent Eight
- Cortex vs NICE Actimize
- Cortex vs Sardine
- Cortex vs Fenergo
- Cortex vs Jumio
- Cortex vs Featurespace ARIC Risk Hub
- Cortex vs Sumsub
- Cortex vs iDenfy
- Cortex vs Shufti Pro
- Cortex vs VMware Carbon Black
- Cortex vs Wireshark
- Cortex vs WorkOS
- Cortex vs Zscaler Internet Access
- Cortex vs Milestone XProtect
- Cortex vs Osano
- ThetaRay vs Backstage
- ThetaRay vs OpsLevel
- ThetaRay vs Earthly
- ThetaRay vs Spacelift
- ThetaRay vs Atlantis
- ThetaRay vs Depot
- ThetaRay vs Nix
- ThetaRay vs SonarQube
- ThetaRay vs Keycloak
- ThetaRay vs Ona (formerly Gitpod)
- ThetaRay vs Vite
- ThetaRay vs Bazel
- ThetaRay vs Dagger
- ThetaRay vs Deep Code
- ThetaRay vs Deno
- ThetaRay vs Fig
- ThetaRay vs Frappe
- ThetaRay vs Git
- ThetaRay vs Feedzai
- ThetaRay vs Unit21
- ThetaRay vs Quantexa
- ThetaRay vs Silent Eight
- ThetaRay vs NICE Actimize
- ThetaRay vs Sardine
- ThetaRay vs Fenergo
- ThetaRay vs Jumio
- ThetaRay vs Featurespace ARIC Risk Hub
- ThetaRay vs Sumsub
- ThetaRay vs iDenfy
- ThetaRay vs Shufti Pro
- ThetaRay vs VMware Carbon Black
- ThetaRay vs Wireshark
- ThetaRay vs WorkOS
- ThetaRay vs Zscaler Internet Access
- ThetaRay vs Milestone XProtect
- ThetaRay vs Osano