EU AI Act and EU Sanctions Squeeze Russian SaaS Companies in Europe

The EU and Russia are tightening the rules for AI businesses almost in lockstep. The Council of the EU has moved forward on the Digital Omnibus on AI, and Russia has published its own draft law. Russian companies selling into the European market now have to account for three layers of restrictions at once: the EU AI Act, EU sanctions, and future national rules. Getting it wrong can cost more than blocked deals: fines can reach 35 million euros.

AI-processed from Habr AI; edited by Hamidun News
EU AI Act and EU Sanctions Squeeze Russian SaaS Companies in Europe
Source: Habr AI. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceHabr AI ↗
Editor-in-Chief
Key metric #1check whether the service falls under the EU AI Act
Key metric #2determine the risk class of AI features and use cases
Key metric #3map regulatory requirements against current EU sanctions

European and Russian approaches to AI regulation have entered a new phase almost simultaneously. For Russian SaaS and B2B companies that sell products in the EU, this means two sets of rules instead of one, layered on top of sanctions that are already in force.

Dates and context

On March 13, 2026, the Council of the EU agreed its position on the Digital Omnibus on AI, a package meant to simplify how the EU AI Act's rules are applied. Just five days later, on March 18, Russia published a draft federal law titled "On the Fundamentals of State Regulation of the Use of Artificial Intelligence Technologies." The timing matters less as a symbol than as a market signal: in both the EU and Russia, AI regulation is moving from broad declarations toward a more practical legal framework.

For companies operating across both jurisdictions, the challenge goes beyond reading new documents. The EU's sanctions regime against Russia already sits on top of the European regulation. According to the article, a ban on supplying enterprise software to Russia has been in effect since December 2023, and a ban on providing AI services since November 2025. As a result, businesses have to look beyond what the AI law permits or prohibits and ask whether they can legally sustain their business model, infrastructure access, and service chain at all.

Where the business barrier lies

The EU AI Act matters for more than European developers. It applies extraterritorially: if a product enters the EU market or affects users and customers in Europe, the requirements may also apply to companies outside the bloc. That makes it mandatory to assess exactly how AI components are built into a product, whether they fall into risk categories, and which documents, oversight processes, and internal policies need to be prepared in advance. Ignoring this is hard, since the article puts maximum fines at 35 million euros.

For Russian SaaS and B2B exporters, this becomes a separate track for managing products and sales. It is no longer a box to tick on a checklist but a series of decisions that shape the roadmap, deal structure, and customer support. This is the point where many companies realize their usual export model no longer works.

At a minimum, businesses will need to answer these questions before actively working in the EU market:

  • check whether the service falls under the EU AI Act
  • determine the risk class of AI features and use cases
  • map regulatory requirements against current EU sanctions
  • separate contracts, infrastructure, and service delivery by jurisdiction
  • budget for ongoing compliance costs, not a one-time audit

In practice, this is no longer a job for lawyers alone. Product teams, sales, architects, and whoever is responsible for model selection, hosting, and customer contracts will all have to make decisions. A feature can look commercially attractive yet prove too expensive or risky to maintain if it requires separate classification procedures, additional documentation, or vendors that Russian companies can no longer work with.

Two legal logics

The core difficulty is that the EU and Russia approach AI with different philosophies. The European model is built around risk assessment, extraterritorial reach, and strict liability for rule violations. Judging by its wording, the Russian draft law sets out basic principles for state regulation of AI use within the country. For businesses, this means they cannot prepare one universal set of documents and call the job done: the requirements, regulatory language, and practical consequences will differ.

As a result, companies operating at the intersection of the two regimes face more than extra paperwork. They have to ask whether they can maintain a single product, legal, and operational setup for all markets at all. If sanctions restrict access to AI services and the EU AI Act demands additional classification and oversight, the decision to enter Europe becomes structural, not just commercial. Sometimes it is cheaper and safer to split operations up front than to try serving everything from one place.

What this means

For Russian AI companies and SaaS exporters, the EU is no longer simply a market with strict rules. It is now a space where they must clear the sanctions filter, meet EU AI Act requirements, and adapt to Russian regulation as it takes shape, all at the same time. That is why exporting an AI product to Europe now starts not with sales and marketing, but with figuring out which delivery scenarios remain legally and operationally viable for the business at all.

Story

Key Questions Answered

What are the key details on Dates and context?

On March 13, 2026, the Council of the EU agreed its position on the Digital Omnibus on AI, a package meant to simplify how the EU AI Act's rules are applied. Just five days later, on March 18, Russia published a draft federal law titled "On the Fundamentals of State Regulation of the Use of Artificial Intelligence Technologies." The timing matters less as a symbol than as a market signal: in both the EU and Russia, AI regulation is moving from broad declarations toward a more practical legal framework. For companies operating across both jurisdictions, the challenge goes be

Where the business barrier lies?

The EU AI Act matters for more than European developers. It applies extraterritorially: if a product enters the EU market or affects users and customers in Europe, the requirements may also apply to companies outside the bloc. That makes it mandatory to assess exactly how AI components are built into a product, whether they fall into risk categories, and which documents, oversight processes, and internal policies need to be prepared in advance. Ignoring this is hard, since the article puts maximum fines at 35 million euros. For Russian SaaS and B2B exporters, this becomes a

What are the key details on Two legal logics?

The core difficulty is that the EU and Russia approach AI with different philosophies. The European model is built around risk assessment, extraterritorial reach, and strict liability for rule violations. Judging by its wording, the Russian draft law sets out basic principles for state regulation of AI use within the country. For businesses, this means they cannot prepare one universal set of documents and call the job done: the requirements, regulatory language, and practical consequences will differ. As a result, companies operating at the intersection of the two regimes

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…