Kobalt Labs
Kobalt Labs automates third party and partner due diligence for banks and fintechs, a compliance function distinct from customer monitoring. Its reasoning engine ingests an institution's own policies, procedures, legal commitments and prior assessments, syncs against external regulation and security standards, then reads a counterparty's contracts and documentation to surface missing clauses, risky language, security gaps and regulatory shortfalls, pulling in beneficial ownership, financing history, adverse news, litigation and enforcement records alongside. It is aimed at community, regional and sponsor banks scaling partner volume, and at fintechs diligencing their own partners.
Capability Axes
Capability grades
15 of 15 axes rated · 4 graded A or B
The reasoning engine is the entire product. It reads a counterparty's contracts and documentation against the institution's own policies, procedures, legal commitments and prior assessments, and against external regulation and security standards, then surfaces the gaps. That comparison is a judgment about unstructured text and cannot be expressed as rules. Without the engine, what remains is a document repository and a checklist, which is precisely the manual diligence process the product exists to replace.
The posture is advisory by construction and the product name says so. The engine surfaces and tracks risks, flags missing clauses and risky language, extracts security information and suggests next steps, while the diligence decision, whether to onboard a partner and on what conditions, stays with the risk officer who signs it. That is the right division for a function where accountability is personal and examinable.
What is not described is the surrounding process: no confidence indication on a flag, no escalation path, no sampling or quality assurance over the reviews, and no account of how a reviewer knows what the engine did not surface.
The published measurement is throughput, and the risk is correctness. Capacity improved fourfold tells a buyer how much faster reviews complete. It says nothing about what proportion of real contractual, security or regulatory gaps the engine detects, which is the only number that matters when the output supports an onboarding decision an examiner will later question. There is no model documentation, evaluation methodology or detection and recall figures, and nothing states support for a customer's own validation.
Distribution is the real validation signal, since no customer is named. An embedded banking platform admitted the company to the partner marketplace it offers its own bank network, and a second technology marketplace lists it. Both involve a vetting step by a party with its reputation at stake. The efficiency claims are more than four times internal diligence capacity and partner diligence completed in a tenth of the usual time.
A co founder describes them as initial benchmarking, meaning self run and early. Team size is reported in single figures, which bears on both evidence depth and delivery capacity for a regulated buyer.
One marketing claim deserves testing rather than acceptance: the platform is described as synchronized with every existing financial regulation, regulatory guidance and security standard. That is a totalizing assertion about a body of rules that changes weekly across dozens of federal, state and international sources. Nothing public describes how that library is maintained or who verifies an interpretation.
Nor does anything say how quickly a rule change propagates, or what the platform does when a regulation is ambiguous. The whole output depends on the currency and correctness of that library, so its maintenance is the central stewardship question, and it is unaddressed.
What this platform ingests is unusual and deserves attention: not customer records but the institution's own internal policies, procedures, legal commitments and previous privacy and compliance assessments. Taken together these are among the most sensitive non customer documents a bank holds and would be highly valuable to an adversary or an examiner's counterparty. Consumer data exposure is correspondingly low, which counts in its favor. There is no published privacy framework, retention schedule or subprocessor list, and no statement on how third party documentation is handled after review.
No trust center, certification list, attestation scope or audit period is published, and the absence has a particular edge. The platform includes a module that extracts and reviews the security posture of third parties on a bank's behalf, so the vendor performs security diligence on others while publishing nothing a buyer can use to perform the same diligence on it. Any bank running its own third party program would ask this vendor for exactly the evidence the vendor helps it demand elsewhere.
As a software supplier, Kobalt Labs holds no license, the expected posture. The function it automates sits directly under interagency expectations for managing third party relationships, which were tightened substantially and which fall hardest on exactly its target buyer, the sponsor bank responsible for oversight of fintech partners it does not control. The product exists because that supervisory pressure made manual partner diligence unscalable. What is missing is specificity. The platform refers to regulation in general rather than naming the particular guidance it is built to satisfy.
The subjects assessed are companies rather than individuals, so consumer fairness is not the frame, but two exposures still apply. The platform surfaces adverse news and enforcement history on counterparties and their beneficial owners. Adverse media coverage is dominated by English language sources, while name matching varies by convention and transliteration, so a counterparty with non Western ownership can draw a different risk picture as a property of the method. Separately, a diligence engine that misses a gap causes a bank to onboard a partner it should have declined. Neither error profile is disclosed.
The harm from a missed gap lands on the bank itself, which onboards a partner it should have declined and answers to its examiner for that decision. A counterparty wrongly flagged as risky loses a banking relationship with no visibility into why. No accuracy commitment, remediation term or correction route is published, and nothing addresses either outcome.
No model providers are named for the reasoning engine, no subprocessor list is published, and nothing describes where a bank's internal policy library and a counterparty's contracts are processed once ingested. The body of regulation the engine matches against is itself an undisclosed supply dependency. The platform claims synchronization with every existing financial regulation and security standard without identifying where that content is sourced or how it is kept current.
Two integration paths are evidenced and both are commercially meaningful for a company this size. Distribution runs through an embedded banking platform's partner marketplace, which places the product inside the procurement path of that platform's bank network rather than requiring each bank to find it, and a second technology marketplace adds another channel.
On the data side the engine connects to business intelligence sources covering beneficial ownership, financing history, adverse news and litigation, so a diligence file assembles itself. There are no named connectors into governance, contract or vendor management systems, and no public developer documentation.
Delivery is cloud hosted software as a service aimed at domestic institutions, so cross border complexity does not arise in the same form it does for global vendors. The question remains, since the platform stores each bank's internal policy library and counterparty documentation. No hosting regions, tenancy model, residency options or subprocessor chain are published.
Pricing is not public: there are no rates, tiers, billing unit or minimum. The gap weighs on this buyer in particular. The target customer is a community, regional or sponsor bank weighing compliance cost against partnership revenue, and the product is sold explicitly as a way to scale partner volume without adding headcount. That is an arithmetic argument that cannot be run without a price on one side of it.
The focus is deliberate and narrow: community, regional and sponsor banks scaling partnership and vendor volume, plus fintechs running diligence on their own partners. Sponsor banks are the sharpest fit, since partner oversight is where supervisory attention has concentrated hardest. Beyond that the coverage stops. There is no material for large banks, credit unions, insurers, asset managers or capital markets, and no evidence of non domestic regulatory coverage. The use case itself is a single compliance function rather than a program.
Alternatives to Kobalt Labs
Other products that do the same kind of work as Kobalt Labs, and what each one does.
Exiger assesses risk in the third parties, suppliers and customers an organization depends on.
Xapien automates the research step of due diligence and returns a document rather than a score.
Intelligo sells AI due diligence and background checks to asset allocators, private equity, real estate, lending and banking clients.
Aptus.AI converts financial regulation into a machine readable format and sells the result to compliance and legal functions at banks, insurers and other regulated firms.
NuArca Labs sells NuComply, a large language model compliance assistant built for banks and other financial institutions.
CleverChain is a London regulatory technology company, founded in 2021, that sells AI agents for due diligence, AML screening and compliance to banks, card providers, private banks, law firms and industrial groups.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
No pricing data has been verified for this vendor. Pricing information will be published here once confirmed through vendor disclosure or third-party estimation.