<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Funding on SoloSoft</title><link>https://www.solosoft.dev/tags/funding/</link><description>Recent content in Funding on SoloSoft</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.solosoft.dev/tags/funding/index.xml" rel="self" type="application/rss+xml"/><item><title>Artemis Raises 70 Million Dollars： The Industry Significance of Using AI to Coun</title><link>https://www.solosoft.dev/trends/2026-04-17-artemis-raises-70-million-to-counter-ai-powered-cy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/trends/2026-04-17-artemis-raises-70-million-to-counter-ai-powered-cy/</guid><description>&lt;h2 id="introduction-when-defenders-start-speaking-the-opponents-language"&gt;Introduction: When Defenders Start Speaking the Opponent&amp;rsquo;s Language&lt;/h2&gt;
&lt;p&gt;The cybersecurity field has long suffered from an asymmetry: attackers need only find one vulnerability, while defenders must protect the entire system. In the past, we relied on layered firewalls, signature updates, and the vigilance of security teams to maintain balance. But the explosion of generative AI is like a master key handed to attackers, instantly pushing this balance to the brink of collapse. Phishing emails become flawless, malicious code can automatically morph to evade detection, and lateral movement post-intrusion can be executed by AI agents.&lt;/p&gt;
&lt;p&gt;It is precisely under this overwhelming asymmetric threat that the emergence of Artemis and its massive funding become so critical. This is not another mediocre story of &amp;ldquo;AI empowerment&amp;rdquo; but a desperate counterattack by the defense side. Its core proposition is simple yet profound: &lt;strong&gt;If the attack chain is already automated, then the defense chain must be too, and it must be faster.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>UK Startups Gather in London to Dialogue with Policymakers, Focusing on AI Regul</title><link>https://www.solosoft.dev/trends/2026-04-16-uk-startups-come-to-london-to-rumble-with-policyma/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/trends/2026-04-16-uk-startups-come-to-london-to-rumble-with-policyma/</guid><description>&lt;h2 id="why-has-dialogue-with-policymakers-become-a-survival-imperative-for-startups"&gt;Why Has &amp;lsquo;Dialogue with Policymakers&amp;rsquo; Become a Survival Imperative for Startups?&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Short answer: Because regulatory costs have shifted from &amp;lsquo;background noise&amp;rsquo; to a &amp;lsquo;survival threshold&amp;rsquo;.&lt;/strong&gt; For startups with annual revenues possibly under £1 million and teams of just over ten people, vague AI ethics guidelines, expensive Standard Essential Patent (SEP) litigation, or sudden data localization requirements can instantly deplete precious cash flow and engineering resources. Startups can no longer focus solely on Product-Market Fit; they must anticipate policy risks in advance and actively participate in rule-making.&lt;/p&gt;
&lt;p&gt;In the past, tech regulatory dialogues were often dominated by tech giants like Google, Meta, and Apple, which have massive compliance teams and even dedicated government relations departments. However, the interests of giants and startups frequently do not align. For example, giants might welcome strict data compliance requirements because they can build moats of capital and technology, blocking resource-poor competitors. According to a &lt;a href="https://www.sbs.ox.ac.uk/research/centres-and-initiatives/oxford-ai/ai-policy"&gt;2025 report from the University of Oxford&amp;rsquo;s Saïd Business School&lt;/a&gt;, over 67% of European AI startups believe that current EU regulatory discussions overly reflect the lobbying positions of large enterprises, failing to consider the implementation costs for SMEs.&lt;/p&gt;</description></item></channel></rss>