TechCrunch, citing The Wall Street Journal, reports that CrowdStrike is buying Fiddler AI and Dreadnode, two startups that monitor and test AI agents, for nearly $500 million; here is what that may mean for founders, and the decision it raises.
If you build products with AI agents (software that carries out tasks on its own for a person or a company), a security company has reportedly just shown what it will pay for two things: watching agents at work and testing them for weaknesses.
TechCrunch reports, citing The Wall Street Journal, that CrowdStrike is buying two startups.1 According to that report, CrowdStrike is paying about $400 million for Fiddler AI, which monitors AI agents inside companies, and about $95 million for Dreadnode, which automates security testing for AI models and agents.1 Security testing means attacking a system on purpose so its weak points can be found and fixed. TechCrunch's headline puts the total at nearly $500 million and describes the market for securing agents as taking off.1
The figures are approximate as reported, and we have not seen the terms of either deal.
The deal sits beside what we have covered: our security roundup reported Elastic's account of intruders using AI tools and SpyCloud's report of malware stealing AI tool logins,2 and our startups roundup reported that the agent funding we covered that week went to startups that keep a person reviewing the work and guard company data.3
So the decision is this: is watching and testing your agents part of what you build from the start, or something you show a customer only after they ask?
What follows is our perspective, drawn only from what we have published. It is where our research begins, not a verdict.
Three of our published patterns bear on this, each with its status mark:
Our research note on running a publication with agents, marked Early, describes each kind of routine work as meant to run on its own only after its record earns it, with a random sample reviewed every week and any correction sending that kind of work back.7
Our hypothesis is an extension of that note, not something it says: a founder could use the same records and checks to decide how much each agent may do on its own. The note describes a publication, not a startup, and none of our pieces measures what customers want or what buyers pay. Our research note on how student founders build companies with agents is Planned: it proposes a study of how student founders build companies this way.8
One reported deal is thin evidence of a market. There is also a serious opposing argument: if large security companies buy these capabilities, monitoring and testing may reach founders as part of larger security products, leaving little reason for a startup to build or show its own, and a founder's scarce time may be better spent on the product itself. Nothing we have published tests this argument either way.
We would revise our view if founders who sell agent products report that customers rarely ask how agents are watched or tested, or if our own patterns, as they move from Early to Running, show that records and checks miss the failures that matter most.
Write one page a customer could read: what your agent may do on its own, what only a person may do, where its actions are recorded, and who hears about a failure. If you cannot write that page, you have found your first piece of work.
For more on founders building with agents, see our Startups section.
This is not legal, financial, or investment advice.![]()
News
Australia Plans an AI Safety Regulator and Mandatory Incident Reporting After an OpenAI Agent Breach