Blackdot Solutions: Videris and investigation software

Blackdot Solutions is a Cambridge-based investigations software company whose Videris products bring external information, analysis and reporting into an organisational workflow. Its public customer record includes a bank, an investigations consultancy and a wildlife-trade monitoring organisation. That breadth helps explain its market role more precisely than the general label of an OSINT company.

The current product family distinguishes Videris Investigate, designed around investigator-led work, from Videris Automate, which applies structured automation to repeatable investigations and reporting. The business is therefore addressing both complex individual cases and the pressure to handle larger workloads. Its relevance to defence and security readers lies in that software and data-management layer, rather than in supplying a military platform.

A Cambridge company with institutional investment

On 6 February 2025, Maven announced that its venture capital trusts had led a £4.5 million investment round in Blackdot. The investor described the company as founded in Cambridge in 2013. It identified product development, automation and AI, technical and business-development recruitment, and international expansion among the planned uses of funding. Maven investment announcement.

The announcement gives a dated financing milestone and an external investor’s description of the growth plan. It does not disclose a complete ownership table or establish that Maven acquired control. The distinction is relevant because Blackdot’s product identity and its shareholder structure answer different questions about the business.

The allocation of funding also provides a useful frame for reading the later product catalogue. Automation was an explicit development priority, while commercial hiring and international expansion concerned how the resulting software would reach organisations. A new product family should therefore be assessed alongside delivery and support capacity, rather than treated as a purely technical change.

What Videris Investigate supplies

Videris Investigate is presented as an environment for collecting information, analysing relationships and producing reports. Blackdot describes an Extension Builder for incorporating internal or specialist sources, alongside analytical tools and exportable outputs. It also says support and training are included with licences. These are product and service descriptions from the supplier. Videris Investigate.

The integration element is central to the commercial proposition. Organisations often have information that is specific to their own work, so a product’s usefulness cannot be judged solely by its standard external sources. An extension mechanism creates a route for the application to accommodate that material without making every investigation a separate software project.

Reporting is another substantive part of the product boundary. An investigation platform must support the handover from an analyst to someone making a decision. Source capture, charts and exportable reports therefore concern how the work is communicated and reviewed, not simply how much material the software can retrieve. Those functions are particularly relevant when several teams contribute to the same case.

Automate changes the workload the company can address

Videris Automate is described as using configured playbooks, external data and AI-supported analysis to produce investigation outputs for human review. Its published use cases include enhanced due diligence, alert resolution, supplier assessment and reporting. The product page emphasises visible sources and a record of decisions. Videris Automate.

This extends the company’s proposition from assisting an investigator through a complex case to helping an organisation structure recurring work. The important comparison is not whether AI appears in the catalogue; it is whether a workflow can be repeated consistently while retaining the information needed to review the result.

For a commercial team assessing Blackdot, the two products imply different adoption conversations. Investigate concerns the working environment of specialist staff. Automate concerns the design of a process that may handle a larger stream of cases. An organisation could have a reason to use both, but the public pages do not establish a single universal deployment pattern or price.

Danske Bank provides a named financial-services example

Blackdot’s Danske Bank case study was originally published in November 2021 and updated in December 2025. It describes the bank’s financial-crime investigation function using Videris to bring together sources and reduce fragmented manual work. The account includes an attributed statement from the bank’s head of suspicious activity reporting. Danske Bank case study.

The dated history matters: a refreshed case-study page is not evidence that the bank first bought the software in 2025. The useful fact is the documented customer relationship and the work described. No contract value or current licence count is published in that account.

Commercially, the example shows Blackdot selling into an established institutional function with a defined output. The relevant product value is the ability to organise investigation work and communicate findings inside the bank. That is a more concrete customer problem than a broad promise to make information searchable, and it offers a basis for comparing the product with other investigation environments.

TRAFFIC shows a different organisational setting

A case study originally published in September 2022 and updated in December 2025 describes use by TRAFFIC, the organisation monitoring wildlife trade. The account places Videris within a wider data-analytics effort addressing environmental crime and natural-resource corruption. It discusses bringing organisational records together with external information and retaining material for reporting. TRAFFIC case study.

This example broadens the company’s documented market beyond financial services. The customer’s subject matter differs, while the underlying software need still concerns multiple sources, analysis and communicable evidence. It suggests why an investigation platform can address several sectors without claiming that their legal mandates or operational practices are identical.

For a security-industry reader, the case is especially useful because it shows adoption outside a conventional defence procurement. Public-interest organisations can have demanding information workflows and can provide specific evidence of product use. Their presence in a supplier’s customer record should be described on its own terms, rather than converted into an implied military endorsement.

CERTA connects software to a professional-services business

Blackdot’s CERTA case study was first published in August 2021 and later updated in December 2025. It describes an investigations consultancy adopting Videris to combine information gathering, visualisation and analysis. Training and more consistent work across a team feature in the account, as do exportable charts used in customer deliverables. CERTA case study.

The consultancy’s attributed statements link the software to assignments it could undertake and work it might previously have outsourced. Those are customer-reported business effects, not independently audited productivity measurements. Even with that boundary, the example is valuable because it connects the product to the economics of a service provider.

A consultancy must turn analyst time into a deliverable another organisation can use. Software that helps maintain consistency and prepare reports can influence that process differently from a stand-alone source subscription. CERTA therefore illustrates a channel of demand in which the end beneficiary of the investigation may not be the organisation buying the software licence.

Position in the wider OSINT market

The ShadowDragon profile examines an adjacent supplier with both application and API routes. Blackdot’s distinguishing emphasis in the records above is the investigation environment and its extension into repeatable workflows. The Ripjar profile offers another comparison, centred more strongly on screening and risk continuity. These are related categories with different starting points.

Blackdot’s strongest public evidence combines an identifiable financing event, two current product families and named customer accounts across distinct sectors. The principal limits are the absence of a complete ownership breakdown, public contract economics and independently measured performance. Future customer-authorised accounts of Automate use, changes to integration support and clearly dated deployment descriptions would make the business easier to assess without relying on broad claims about AI or market size.