Ripjar: risk screening, Labyrinth and intelligence software

Ripjar is a UK software company headquartered in Cheltenham, with a product portfolio spanning customer screening, adverse-media analysis and threat investigations. Its public identity connects a background in intelligence to financial-crime compliance. The commercial story is clearest when those origins are separated from what the company now sells: software that helps organisations maintain risk information, review alerts and investigate more complex material.

The current product family includes Ripjar Screening, Screening Assistant and Labyrinth. These address related but different workloads. Screening concerns repeated assessment across an organisation’s customer or counterparty population; an investigation environment supports more developed analysis. That distinction gives a defence-industry reader a useful way to locate Ripjar within the wider intelligence software market.

Origins, capital and strategic relationships

Ripjar’s company page says it was founded in 2013 by a team from GCHQ. Its current headquarters are in Cheltenham. This establishes the company’s stated origin and location; it does not mean that a present commercial deployment is an intelligence-agency programme. About Ripjar.

A dated announcement on 16 September 2020 reported a $36.8 million, or £28 million, Series B led by Long Ridge Equity Partners, alongside existing investors Winton and Accenture. Ripjar said total funding then exceeded $60 million. Those figures describe a historical financing event, rather than the company’s current valuation or cumulative funding as of September 2026. Series B announcement.

On 6 January 2023, the company announced a new strategic partnership with Dow Jones, describing cooperation that had begun in 2018. The release also included a Dow Jones statement about its investment in Ripjar, without publishing an amount or ownership percentage. This adds a named information-provider relationship to the financial-investor record. Dow Jones partnership.

The two relationships illuminate different parts of the business. Capital supports company development, while a data-provider partnership can affect the offering presented to customers. They should not be collapsed into a single ownership claim. The complete current shareholder structure is not disclosed in these public releases.

Screening as a continuing record

Ripjar Screening is organised around the idea of an entity profile that retains relevant context and previous decisions. The product page describes sanctions, politically exposed person data, watchlists and adverse media being brought into that continuing record. It also presents integration with different external providers and an organisation’s own data. Ripjar Screening.

The commercial problem is recognisable: a large organisation does not want every new item of information to erase what its staff have already established. Retaining context can make the software part of an ongoing operating process rather than a succession of disconnected searches. That is the proposition being sold; the precise effect on workload depends on the deployment.

This emphasis also distinguishes screening from a general search or research application. The product must accommodate repeated review across an existing population and preserve the rationale for decisions. A customer evaluating it therefore has reasons to examine how it fits established records and review responsibilities, alongside the range of sources it can process.

Identity context is part of the product’s evolution

A July 2024 Ripjar article explains the use of location context in adverse-media identity matching. The company describes the problem of deciding whether material concerns the relevant entity when names alone are ambiguous. Its published approach adds contextual information to that assessment. Location-context product discussion.

This is a useful company-specific development because it shows where product work is being directed. More information is not automatically more useful if it produces repeated ambiguity. The value proposition concerns how the software helps distinguish relevant from irrelevant material while retaining an understandable record.

For a business reader, that makes entity resolution a commercial capability as well as a technical feature. It can affect the amount of review work created by a data feed and the confidence with which one team hands an assessment to another. Ripjar’s article supplies its own account of the feature; it is not a comparative independent benchmark against competing systems.

Screening Assistant addresses the review workload

The current portfolio presents Screening Assistant as an AI-supported capability for reviewing alerts, resolving lower-risk items within configured processes and escalating cases with supporting evidence. The product is positioned alongside Screening rather than as a replacement for the organisation’s responsibility to make decisions. Current screening and assistant portfolio.

That packaging reflects a different question from whether a screening engine can find a possible match. Once an alert exists, someone must understand it, decide what follows and preserve the reasoning. The assistant product is aimed at that second workload. Its commercial significance lies in the handover between generated alerts and completed reviews.

The relevant comparison with other AI software is consequently the place where it enters the process. A tool summarising a document, a system generating an alert and an assistant helping resolve that alert may all use language technology, but they do not perform the same organisational job. The Primer profile provides a neighbouring example of software built around transforming and analysing material for users.

An anonymous bank case gives process detail

Ripjar published a Tier 2 bank case study on 19 May 2026. It describes a move away from an article-oriented, on-premises approach toward cloud-based screening using Dynamic Risk Profiles and a combined view of adverse media and watchlist information. The bank is not named in the public account. Tier 2 bank case study.

The useful evidence is the described change in workflow and architecture. It shows the kind of customer problem the supplier is addressing: fragmented review, repeated context gathering and the management of an expanding screening workload. The case’s anonymity limits independent identification of the deployment, and its headline performance figures should be treated as vendor-published claims.

Even with that limit, the account contributes more than a generic sector label. It explains a proposed migration from handling individual items to maintaining continuing entity context. That is a concrete commercial proposition which can be compared with a prospective customer’s existing process without adopting a promised percentage saving.

Labyrinth connects to enterprise security data

Ripjar announced an integration with Amazon Security Lake on 31 May 2023 for Labyrinth for Threat Investigations. The announcement described bringing internal security information together with other relevant data for investigation workflows. This identifies a specific cloud ecosystem connection for the Labyrinth side of the portfolio. Amazon Security Lake integration.

The integration expands the picture beyond financial screening. An enterprise investigation environment may need to work with data already held in an organisation’s security infrastructure. Compatibility with that environment can influence adoption as much as the standalone application’s features. The announcement establishes an integration, rather than identifying a new government contract.

It also illustrates why platform relationships deserve separate attention from customer logos. A cloud integration can make a product easier to fit into a software estate, while a data-provider partnership can change the information available within it. Neither relationship alone establishes the revenue generated by a particular deployment, but both help explain the supplier’s route to market.

A specialist positioned between data and decisions

The Blackdot Solutions profile offers a useful comparison around investigator-led work and automated reporting. Ripjar’s documented emphasis is stronger on continuing screening, entity context and the review of generated alerts, with Labyrinth extending into broader threat investigations. The categories overlap, but their starting workloads differ.

The available evidence supports a company with historical institutional investment, a named Dow Jones relationship, an identified cloud integration and a developed screening product family. It does not disclose full ownership percentages, customer-by-customer economics or independently validated performance. The most informative future records would be named deployment accounts, clearly described product migrations and dated partner arrangements showing how the software becomes part of an organisation’s continuing work.