Horizon3 raises $250M at $2B valuation as AI threats escalate

Horizon3 triples valuation to $2 billion with $250M Series E as enterprises race to test AI defenses against escalating threats.

By Central
Horizon3 raises $250M at $2B valuation, reflecting soaring demand for autonomous penetration testing amid AI-driven attacks.
Highlights
  • Horizon3 has raised $250 million in Series E funding at a $2 billion valuation.
  • The company's NodeZero platform has conducted over 310,000 production security tests with zero disruptions.
  • Horizon3 expects to accelerate growth after reaching nearly $100 million in annual recurring revenue.

You are a Senior Editorial Writer and Editor-in-Chief for a major English-language digital publishing company. Write a complete, authoritative, and professionally structured article in English.

OUTPUT RULE: Return ONLY the final HTML article. No explanations. No comments. No notes. No text outside the article. No Markdown. No symbols like *, **, #.

INPUTS:
TITLE: Horizon3 raises $250M at $2B valuation as AI threats escalate
CONTENT:

Cybersecurity startup Horizon3 has raised a $250 million Series E at a $2 billion valuation, more than tripling its valuation in 14 months. The San Francisco-based firm drew backing from returning investors NightDragon and NEA.

The funding arrives as two major AI research labs disclosed last week that their models had breached systems outside their intended scope. Horizon3, which has spent six years building AI specifically designed to probe networks for vulnerabilities in a controlled, authorized manner, is riding growing enterprise demand. With AI-driven attacks accelerating, enterprises are rushing to stress-test their defenses at scale, a gap that traditional security vendors have largely left unfilled.

Matt Hartley, the company’s chief revenue officer, said that its NodeZero platform has two core strengths: It can test live systems without shutting down operations, a capability other AI-powered tools have struggled to deliver reliably, and it scans an entire infrastructure continuously rather than once a year, examining the full network rather than just 2-3%.

The company approached $100 million in annual recurring revenue last year with 120% year-over-year growth, and expects to accelerate growth this year, Hartley said.

AI tools have made it easier for attackers to develop new exploits quickly, forcing security teams to handle threats faster than they can fix them. Horizon3 spent roughly $100 million in R&D building automated systems designed to stay predictable and controllable, Hartley said. That’s significant given recent breaches at AI labs, which raised questions about whether any AI system can truly remain contained.

“It’s also making people a lot more careful about how they deploy AI,” Hartley said. “We’re getting a lot of questions today around: Can you detect AI? Of course we can. But I think a lot of organizations that rushed to deploy AI across the enterprise are now thinking twice about the ramifications of those deployments; what if my own security team gets too aggressive, could there be unintended consequences? So a lot of organizations are moving into what I’d call a bold new world, which is exactly why you need consistent, predictable testing from a company like Horizon3, to know how to strengthen your own defenses against real-world exploits.”

In a statement, Horizon3 has run 310,000 production security tests with zero disruptions, establishing what it calls “AI Hackers,” fully autonomous penetration testing.

The real competition isn’t other software vendors; it’s the existing model, according to Hartley. Most companies hire human security firms to run annual tests and those won’t disappear, he continued. What’s shifting is what clients demand after signing up: Instead of sampling 5% of infrastructure once yearly, they now want to scan everything monthly or weekly, tracking whether they’re actually getting safer.

Horizon3’s founders, Snehal Antani and Anthony Pillitiere, met while serving at Joint Special Operations Command, where they saw firsthand how resource constraints made continuous security testing difficult. They founded Horizon3 to automate those repetitive assessments.

With the funding, Horizon3 is expanding internationally, including new offices in Amsterdam (in June 2026), Australia, and Singapore, while building a partner network and maintaining substantial R&D spending.  

Strategic investors now include Singapore’s EDBI, defense contractor SAIC, and Qualcomm, signaling that the vulnerability they’re addressing extends well beyond any single sector.

Horizon3 has roughly 7,200 to 7,300 customers, ranging from managed service providers serving small businesses to Fortune 10 enterprises. The company claims an addressable market of tens of billions of dollars, a figure that aligns with industry estimates of the broader cybersecurity market, valued at $271.9 billion in 2025 and projected to reach $663.2 billion by 2033, according to Grand View Research.

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

LANGUAGE: Write entirely in English. Preserve proper nouns, brand names, product names, game titles, technologies, and technical terms exactly as written. Translate everything else naturally. Read as if written by a native English editor.

CONTENT SOURCE: Treat CONTENT as your primary factual source. Build the article from deep understanding of CONTENT. Do not mechanically expand the title.

CONTENT CLEANING: Remove website names, publication names, author credits, RSS labels, newsletter markers, syndication branding, generic labels (Summary, Highlights, Recap, Key Takeaways). Convert “according to X” into direct factual statements.

FACT PRESERVATION: Preserve exactly: names, brands, companies, products, games, technologies, dates, numbers, percentages, prices, technical specifications. Never distort facts.

WRITING STYLE: Natural, fluent, authoritative, engaging, analytical, trustworthy, nuanced. Blend factual reporting, explanation, contextualization, analysis, practical interpretation, and strategic insight. Vary paragraph length and sentence structure. Avoid robotic phrasing, repetition, clichés, promotional language, filler sentences.

ARTICLE LENGTH: Long-form, highly detailed. Target 1,500-3,500 words. Feel comprehensive and substantive. Never feel brief, superficial, or summary-like. Expand naturally with historical background, industry context, technical explanation, market implications, strategic significance, practical consequences, comparisons, future outlook — but only when content genuinely supports it.

STRUCTURE:
– Begin with a

introduction. No heading before the first paragraph.
– Introduction must hook the reader within 2-3 sentences.
– Use

,

,

only when they improve organization.
– Each section must introduce meaningful new information.
– Closing: end with a forward-looking, analytical, or practical paragraph.
– Never use generic closing headings like “Conclusion”, “Summary”, “Final Thoughts”, “Looking Ahead”, “What Comes Next”, “Takeaway”, “Key Points”.

HEADINGS: Write content first, then generate headings. Headings must be specific, concrete, informative, and editorial. They should reference actual events, features, numbers, dates, or companies. Support SEO naturally.

SEO + AEO + GEO + E-E-A-T:
– Integrate primary keyword naturally in first paragraph and in at least one h2.
– Use semantically related terms throughout.
– Anticipate questions English-speaking users would ask. Answer them directly: “What is…”, “How does…”, “Why did…”, “When did…”, “What are the…”
– At least one section must provide a clear, standalone answer (2-4 sentences) formatted for a featured snippet. Place the answer immediately after the question.
– Include geographic context only when directly relevant.
– Show expertise by explaining mechanisms, causes, and implications — not just stating facts.
– Build authority through precise, well-contextualized information.
– Establish trust through accurate facts, balanced tone, measured claims.
– Never write “experts say” or “studies show” without specific grounding in the content.

INTERNAL PROCESS (do not output this):
1. Analyze: content type, search intent, technical level, topic complexity
2. Determine ideal length (1,500-3,500 words based on complexity)
3. Adapt tone: Journalistic / Analytical / Explanatory / Consultative / Technical / Conversational Professional
4. Clean sources and preserve all facts
5. Write article with proper structure, headings, and AEO snippet
6. Validate: grammar, fluency, coherence, depth, no repetition, valid HTML, facts preserved, no generic headings

HTML RULES: Use ONLY:

  1. . Valid, clean HTML. No inline styles. No unnecessary whitespace.

    FINAL CHECK: If the article sounds translated, mechanical, superficial, or incomplete — rewrite completely.

    OUTPUT: Return ONLY the final HTML article, beginning with

    .

Share This Article