In early 2022, Russian tech firms got cut off from the platforms they had run on for decades. Microsoft, SAP, Oracle, AWS, and the whole universe of SaaS tools stopped selling, pulled support, and shut down cloud access. The story outside Russia made it sound like a knockout punch. On the ground, it felt different. Companies didn’t collapse. They reorganized. A few moved shockingly fast. Others are still grinding through transitions that hurt. I want to walk through what actually happened—what got replaced, what got built, and where everything still feels like it’s held together with tape.
The Immediate Shock and the Licensing Void
The first mess was licensing. Big enterprises running SAP or Oracle databases woke up to blocked renewals and no way to add seats. The software itself still worked—licenses bought before the cutoff were technically valid—but no updates, no patches, and a cloud of legal uncertainty. Some shops ran unlicensed copies and just swallowed the security risk. Others finally launched migration plans that had been sitting in PowerPoint decks for years.
Almost overnight, system integrators who used to be the local face of SAP or Oracle reinvented themselves as independent support guns for hire. Their days now are a grind of reverse-engineering patches, writing custom security fixes, and coaching in-house teams on codebases with no updated docs. It’s expensive. It’s fragile. But it has kept the lights on in energy, banking, and heavy manufacturing.
The Rise of Domestic Alternatives: A Mixed Picture
The government’s import substitution push started almost a decade earlier, but the results were patchy. The forced break changed that. Homegrown platforms grabbed market share fast. Here’s how it broke down by category.
Operating Systems and Office Software
This is the most settled part of the story. Astra Linux and ALT Linux, both Debian-based and built in Russia, got pulled into enterprise environments quickly. They aren’t knockoffs—they carry their own security modules and government-mandated compliance certifications. On the office side, MyOffice and P7-Office stepped in for Microsoft 365 inside state agencies and state-owned firms. The private sector dragged its feet. File compatibility was a headache, and muscle memory is hard to fight. But once Microsoft 365 subscriptions became impossible to renew, mid-sized businesses switched too. It helped that these Russian suites support ODF and have gotten decent at handling legacy .docx files.
ERP and Business Management
Here’s where things get sticky. 1C Company already owned the Russian market for accounting and basic enterprise management, but its ERP line was built for mid-sized firms, not globe-spanning operations. After 2022, 1C threw resources at scaling up—adding manufacturing execution, real logistics depth, and HR modules that used to be SAP or Oracle territory. What’s running now in big industrial groups is a hybrid beast: core financials on 1C, with custom bridges to legacy SAP instances kept quarantined and unpatched. It’s clumsy architecture. It works. A full SAP-to-1C migration for a 50,000-employee company is a two-to-three-year, tens-of-millions-of-dollars ordeal. Most firms are stretching that cost across years.
Cloud Infrastructure and Virtualization
When AWS, Azure, and Google Cloud pulled out, the gap looked terrifying. Yandex Cloud and VK Cloud Solutions stepped up hard. Yandex Cloud, in particular, built out managed Kubernetes, managed PostgreSQL, and object storage that speaks the S3 API, which made moving from AWS less of a nightmare than I expected. There are rough edges: the CDN barely reaches outside the CIS, and some advanced analytics services are still missing. But for domestic workloads, it’s a real platform now. On the virtualization side, the VMware license cutoff shoved companies toward open-source KVM and a Russian product called zVirt. IT teams had to rebuild hypervisor stacks while production systems ran on temporary VMware environments that can’t be patched. Not for the faint of heart.
Hardware Dependency: The Deeper Constraint
Software is only half the picture. The iron underneath matters just as much. Western semiconductor sanctions hit Russian data centers directly. You couldn’t just order new servers from Dell, HPE, or Lenovo with Intel and AMD inside. The workaround came in three waves. First, parallel imports through Kazakhstan, Turkey, and the UAE brought in servers at a 20–40% markup. Second, local assemblers like Aquarius and Yadro scaled up with whatever chips they could get, often a generation or two behind. Third, some outfits started testing Baikal and Elbrus processors—Russian-designed CPUs—but those are fabbed at process nodes five to seven years behind the cutting edge. For serious compute, they aren’t ready. The result on the ground: Russian IT shops now design systems to run lean on older or weaker hardware. That means real code optimization and a forced move away from bloated architectures. This hardware ceiling is reshaping engineering culture more than any government directive ever could.
The Open Source Forking Strategy
One adaptation that doesn’t get enough attention is the deliberate, methodical use of open source. Russian companies were already deep into Linux, PostgreSQL, and Kubernetes. Once sanctions hit, Red Hat and Canonical support vanished, and GitHub locked out some organizations. The move was to fork critical projects and build internal support muscle. SberTech, Sberbank’s tech arm, built Platform V—a suite of forked open-source components with proprietary security hardening. The National Open Source Software Platform, backed by the government, now hosts forks of essential libraries and tools maintained by teams that audit for vulnerabilities and guarantee availability independent of Western maintainers. This approach has ruffled feathers in the global open-source community. From a pure survival standpoint, it has kept development pipelines breathing.
Mobile Ecosystems and the Android Problem
Google cutting off Google Mobile Services licensing for Russian OEMs created a distinct mobile headache. Developers can still use the Android Open Source Project, but without GMS, apps lose push notifications, maps, and payment plumbing. Russia’s answer is Aurora OS—a Sailfish-based mobile platform from Rostelecom—and the RuStore app marketplace from VK. Right now, Aurora lives on government and corporate devices, not consumer phones. The app catalog is sparse: banking apps, corporate messengers, document viewers. Consumer services are barely present. The long game is a parallel mobile stack with zero dependence on American services. That’s a decade-long project. In the meantime, most Russian users and companies use Android devices imported through parallel channels, with GMS enabled by third-party activation services. Everyone knows it’s a fragile crutch. Nobody can fix it fast.
Cybersecurity in a Disconnected Environment
When Western security vendors like Palo Alto Networks, Fortinet, and CrowdStrike pulled out, Russian organizations lost threat intelligence feeds and signature updates overnight. The adaptation ran on two tracks. Kaspersky and Positive Technologies grew their enterprise offerings, but they also had to rethink their threat models. With less visibility into global attack patterns, they leaned into behavioral detection and internal network monitoring instead of depending on external data. Companies built internal SOCs that operate with more autonomy. The upside is a deeper investment in security fundamentals—network segmentation, tight access controls, regular penetration testing—rather than trusting vendor black boxes. The downside, which nobody likes to discuss, is a likely accumulation of undetected advanced threats that won’t surface for years.
The Talent Equation
Adaptation is, in the end, about people. The IT labor market in Russia contracted sharply in 2022 when tens of thousands of developers and engineers left. Those who stayed faced a new demand signal: less work on global product teams, more work on rebuilding infrastructure from the ground up. Salaries for specialists who knew 1C, Astra Linux, and Russian cloud platforms jumped 30–50%. Companies poured money into retraining, converting Java and .NET developers to the domestic stack. The brain drain hasn’t stopped, but it has slowed. Some who left now work remotely for Russian firms from Kazakhstan, Armenia, or Georgia, navigating a gray zone around sanctions. This scattered workforce is now a structural fact of the industry.
What Hasn’t Been Solved
A few problems are still raw. First, CAD/CAM and engineering software: replacements for Autodesk, Dassault Systèmes, and Ansys lag badly. Russian tools like KOMPAS-3D and T-FLEX CAD have improved, but they lack the simulation and collaboration depth global engineering teams expect. Second, AI and machine learning frameworks: PyTorch and TensorFlow are open source, yes, but the GPU hardware to run large-scale training is not easy to get. Third, international collaboration: Russian IT firms that once served global clients have lost nearly all that business. The domestic market is big enough to survive on, but not big enough to fuel the kind of growth the industry saw in the 2010s.
Frequently Asked Questions
Are Russian companies still using pirated Western software?
Some are, especially small and mid-sized businesses that can’t afford a migration. Big enterprises and state-linked entities have largely moved to legal domestic options or run legacy licensed versions without updates. The government hasn’t openly blessed piracy, but enforcement of IP from “unfriendly” countries is essentially zero. The real risk isn’t legal—it’s technical. Unpatched software is a security debt that compounds over time.
How long will it take for Russian IT platforms to become globally competitive?
In operating systems and office suites, the gap is closing and could hit near-parity for domestic use in three to five years. In ERP, cloud services, and engineering software, the distance is still wide. Global competitiveness would need more than feature parity—it would need integration with international standards and ecosystems that sanctions make extremely hard. A realistic timeline for globally competitive products is a decade or more, and only if the hardware constraints loosen.
What happens if sanctions are lifted tomorrow?
Re-entry wouldn’t be instant. Contracts, trust, and integration pipelines would need rebuilding. Some companies would stick with domestic solutions for core systems simply because they’ve already paid the migration cost. Others would rush back to Western platforms for advanced features. The most likely outcome is a hybrid mess for years: Russian platforms handling regulated or sensitive workloads, Western platforms used where performance and global compatibility matter. The adaptation isn’t easily reversible—it has already created new institutional muscle memory and sunk costs that won’t vanish with a policy change.