Cohere buys two security startups to add cyber defense and secure code review
AISLE becomes Cohere Cyber, while cubic keeps its product running. Both additions target organizations that need AI inside tightly controlled infrastructure.
Loading page…
AISLE becomes Cohere Cyber, while cubic keeps its product running. Both additions target organizations that need AI inside tightly controlled infrastructure.
Listen to this story
The acquisitions extend Cohere’s enterprise offering into two stages of software security: finding vulnerabilities in deployed systems through AISLE and reviewing code changes through cubic. Both teams are being positioned to serve organizations that require private-cloud, on-premises or air-gapped deployments, giving Cohere a security-focused route into tightly controlled environments. AISLE’s transaction closed November 10, while cubic confirmed its acquisition on November 13; financial terms were not disclosed.
AISLE reported finding more than 650 vulnerabilities assigned CVE identifiers in the 14 months before its November 10 announcement, according to Unite.AI.
Cohere says cubic’s code-review platform can identify and automatically remediate bugs and vulnerabilities; its product will remain available and supported.
AISLE co-founder Ondrej Vlcek will lead Cohere Cyber, while co-founder Jaya Baloo becomes Cohere’s chief information security officer and Stanislav Fort leads AI security research.
Cohere is bringing software security into its enterprise AI business through two acquisitions announced as complete on November 13, 2026. Its announcement adds AISLE’s vulnerability-discovery systems and cubic’s AI code review, pairing cyber defense with secure development for enterprises and governments that want to keep AI—and the data it handles—under their control.
Financial terms were not disclosed. The announcement joins two transaction timelines: AISLE said its acquisition formally closed on November 10, when it began serving customers as Cohere Cyber. Cubic separately confirmed its acquisition on November 13.
AISLE’s work targets previously unknown weaknesses in complex software already in production. Its approach combines foundation models with specialist security knowledge and large-scale code analysis. The process includes validating a suspected vulnerability and assisting with a fix, rather than stopping at a warning that something might be wrong.
AISLE reported that its platform discovered more than 650 vulnerabilities assigned CVE identifiers in the 14 months before its November 10 announcement, according to Unite.AI.
Cubic addresses the review of code changes and the wider task of understanding a codebase. Cohere says its platform can find bugs and security vulnerabilities and automatically remediate issues. Founder and CEO Paul Sanglé-Ferrière and his team will help integrate enterprise coding capabilities into Cohere’s platform.
Cohere positions both additions around organizations requiring private-cloud, on-premises or air-gapped deployments—networks isolated from external connections. It specifically describes cubic’s review agents as built for on-premises and air-gapped environments. Cohere calls its approach sovereign AI: organizations retain ownership of their data, infrastructure and operations while using advanced AI.
AISLE’s three co-founders are taking leadership roles across the new business, corporate security and AI research:
Cohere also plans a substantial long-term investment in Prague, expanding AISLE’s existing presence. The city is intended to become its global center for AI cybersecurity and autonomous security systems.
For existing cubic customers, the immediate commitment is continuity: the company says its product will remain available and fully supported. Its team will keep developing it inside Cohere, with further improvements planned.
Loading discussion...
Join the conversation
Explain whether closer integration or a separate security provider would give you more confidence.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.