Cohere Moves to Buy AISLE, Silent on Users Running It in Bedrock

If your security team runs AISLE, or is piloting it against other AI vulnerability scanners, the product you bought now has a buyer and no written plan for your deployment. Cohere signed a letter of intent to acquire AISLE on October 15, 2026 and will fold it into a new unit called Cohere Cyber. Neither company has published a price, a closing date, which models the product will run, or what happens to the option of running AISLE inside your own Bedrock, Foundry or Vertex account. The one line for customers is that the "focus remains on continuity and stronger products". That leaves you a window to get model choice, deployment options and change-of-control terms in writing before the deal closes.

What Cohere Has Actually Agreed To Buy

Cohere has signed a letter of intent, which is the stage before a definitive purchase agreement, and nothing more has been announced. AISLE's own post says the two companies signed an LOI and that more details "will be shared as the transaction progresses." Reuters reported that the terms were not disclosed, and The Logic and PYMNTS carry no price either.

What is on paper is the org chart. Per Cohere's announcement:

• Ondrej Vlcek, AISLE's CEO and the former CEO of Avast, becomes Senior Vice President of Cohere Cyber.
• Jaya Baloo becomes Cohere's Chief Information Security Officer for the whole company.
• Stanislav Fort becomes Vice President, AI Security, and joins Cohere's core model research and training.
• Cohere plans a "substantial long-term investment in Prague," which it says becomes AISLE's global center for AI cybersecurity.

Read that list as a buyer. Two of the three founders move into roles that serve Cohere broadly, as company CISO and as a model-research lead. Only Vlcek stays on a customer-facing security product line, and that line is a new business unit with no published product list.

Why Cohere Wants a Vulnerability Scanner

Cohere is buying AISLE's track record, and the track record is strong on paper. According to Cohere, in its first year out of stealth AISLE found more than 500 previously unknown vulnerabilities that received CVEs across more than 100 codebases, including all 12 vulnerabilities in OpenSSL's January security release and 18 of the 24 CVEs in curl's latest release. Cohere says maintainers reviewed those findings independently. AISLE's homepage quotes Bruce Schneier crediting it with "13 of 14 OpenSSL CVEs assigned in 2025."

The Logic notes that Cohere's models trail OpenAI's and Anthropic's in coding and cybersecurity, and quotes Cohere CEO Aidan Gomez from a September interview: "There's a gap today, and we want to work to close that." Reuters says the deal would add cybersecurity to the group Cohere is assembling with Germany's Aleph Alpha. Cohere is positioning itself as the sovereign option for governments and regulated industries, and a credible offensive-grade scanner gives it something to sell into security budgets that a chat model does not.

Treat AISLE's product metrics as vendor claims. The homepage lists a 91% true positive rate, 85% of proposed fixes accepted by developers and "10x cost-efficiency vs. Mythos," with no methodology on the page. The Snapshot launch release from June 10, 2026 adds a false positive rate under 5% and a #1 ranking in three categories of a UC Berkeley benchmark, also self-reported. The CVE counts are the part a third party can check.

---

The Deployment Question Nobody Has Answered

AISLE sells four places to run it, and Cohere's announcement names three environments, none of them a hyperscaler. AISLE's homepage lists "Our Cloud" (fully managed), "Your Cloud (Bedrock · Foundry · Vertex)", on-premises and air-gapped, and says customers can "use AISLE's optimized AI models or bring your own." Cohere's post promises secure deployments in "private cloud, on-premises, and fully air-gapped environments." It does not mention Amazon Bedrock, Microsoft Foundry or Google Vertex AI by name, and it does not say whether "private cloud" includes a customer's own hyperscaler account.

That gap matters because of how the "Your Cloud" option works. If AISLE runs inside your hyperscaler account, it uses models that account can reach. An owner whose business is selling its own models has an obvious reason to steer the product toward them. Today, AWS's Bedrock catalog of Cohere models lists Command R, Command R+ and embedding and rerank models, and does not list Command A. If Cohere Cyber standardizes on Cohere's current generation, a Bedrock deployment either keeps a non-Cohere model path alive or waits for Cohere to ship there.

AISLE's own history argues the model matters less than the system around it. In April, SD Times reported that AISLE showed vulnerability discovery working with "free, open-source, small LLMs running in parallel," and quoted the company's view that the surrounding system is the key factor. The Snapshot release says AISLE matches each task to a suitable model rather than defaulting to a frontier model. That is the strongest argument that the product survives a model swap. It is also a reason to keep the timing of any swap in your own contract.

The steel-man for Cohere is real. Its whole pitch is private and air-gapped deployment, it already sells Cohere North on that basis, and a security product built for code that cannot leave the building fits that pitch well. Customers who run AISLE on-prem or air-gapped may get more investment after the deal than before it. The exposure sits with customers on the managed cloud or the hyperscaler path, and with anyone who chose AISLE because it let them bring their own model.

How Long a Cohere Deal Takes to Close

Cohere's last European deal suggests you have months, though nobody has said how many. Cohere and Aleph Alpha announced plans to combine in April, then announced the definitive business combination agreement on September 16, 2026, about five months later. BetaKit reported that deal is still subject to regulatory approvals and expected to close later in 2026. We covered the original announcement in Cohere-Aleph Alpha $20B Deal Reshapes Sovereign AI.

AISLE is a much smaller transaction, and a small private deal can move faster. Still, the AISLE announcement is at the same stage the Aleph Alpha deal was in April: intent, no definitive agreement, no price. Every renewal or expansion you sign in that window is signed with today's AISLE, under today's terms, while the people who will run the product are already named into Cohere roles.

Your contract is the only lever you have before closing. Standard AI vendor terms are thin here; our review of exit clauses found standard terms give 0 to 90 days to get out after a model deprecation or ownership change.

Where AISLE Sits Among the Alternatives

The AI vulnerability discovery market is crowded with large owners, which changes how much leverage AISLE customers have. Anthropic launched a scanner for open-source maintainers that we found skips human review and the public advisory. OpenAI's Codex Security Cloud scans new commits with no per-scan price. Snyk Evo and Sonar Vortex sit on the AppSec side.

AISLE's differentiators were a flat price that, per its Snapshot release, does not scale with token consumption, and deployment wherever your code lives. Both are exactly the terms a new owner could change. If you are mid-evaluation, those are the two things to score AISLE on, and the two things to get pinned before you pick it.

---

What to Do Before the Deal Closes

This Week:

1. Pull your AISLE order form and master agreement and find three clauses: assignment, change of control, and termination for convenience. Write down whether a change of control gives you a termination right and how many days of notice it requires.
2. Ask your AISLE account team, in writing, which models your deployment runs today and whether that includes a model you supplied. Save the answer; it is your baseline.
3. If you run AISLE in Bedrock, Foundry or Vertex, ask whether that deployment option is on Cohere Cyber's roadmap. "Continuity" is the current answer, so ask for a date.

This Month:

1. Before any renewal or expansion, add a rider that freezes the current deployment option and model choice (including bring-your-own-model) for the full term, with a termination right and pro-rata refund if either changes.
2. Add flat-price protection. AISLE's pricing does not scale with tokens today; write that into the order form so a move onto Cohere's metering cannot reprice you mid-term.
3. Export your findings, triage history and accepted fixes into your own ticketing system, so a platform migration does not cost you your vulnerability history.
4. If you are evaluating AISLE now, run the bake-off anyway. The CVE record holds up. Weight your score toward the terms you can lock into the contract.

Before Closing:

1. Ask Cohere directly whether AISLE customer data, including your source code and findings, will be used to train Cohere models. Fort's move into core model training makes this a fair question.
2. Confirm the sub-processor list will not change without notice, and that Prague remains a processing location if your data residency analysis depends on it.

The Bottom Line

AISLE's scanner runs on models, and its new owner sells models, so the model question will come up whether or not anyone plans it. Cohere has a credible reason to keep AISLE running everywhere its customers need it, particularly on-prem and air-gapped. It has not said so for the hyperscaler path, and while the deal sits at the LOI stage you still have the leverage to ask for it in a contract.

Get the deployment option and model choice written into your next order form before the definitive agreement is signed.

Continue Reading

• Cohere-Aleph Alpha $20B Deal Reshapes Sovereign AI
• Cohere North 2 Gives Agents Memory and Names No Retention Rule
• AI Vendor Exit Clauses: Standard Terms Give 0 to 90 Days to Get Out
• Anthropic's OSS Scanner Skips Human Review and the Public Advisory
• Codex Security Cloud Scans New Commits With No Per-Scan Price
• Proofpoint Buys Varonis for $6.3B as On-Prem Support Ends Dec. 31
• Stilla Promised Continuity. Meta Bought It for WhatsApp.