Live Nov 18 · Cohort 3Nov 18, 19:00 MSK — free hands-on AI agents live workshop · Live Cohort 3 starts Nov 23Join Nov 18 Live →Cohort 3 (Nov 23)
ReleaseInsight · On RadarCNews ИИ→ original

Rostelecom Announces Nearly 7 Billion Rubles in Purchases of Russian-Made Equipment

Rostelecom and RTK-TsOD have announced tenders worth nearly 7 billion rubles: they need hundreds of servers, dozens of data storage systems and switches. All equipment must be listed in the registry of Russian products. For engineers this means a limited choice of platforms, while for domestic suppliers it is a major chance to prove performance and compatibility in real infrastructure.

AI-processed from CNews ИИ; edited by Hamidun News
Rostelecom Announces Nearly 7 Billion Rubles in Purchases of Russian-Made Equipment
Source: CNews ИИ. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceCNews ИИ ↗
Editor-in-Chief
Key metric #1Nearly 7 billion rubles is the starting price of the tenders, not the final payout.
Key metric #2The purchase includes servers, data storage systems and switches.
Key metric #3The customers have not disclosed the exact delivery addresses.

Nearly 7 billion rubles is the starting price of the new tenders from Rostelecom and RTK-TsOD for server and network equipment. This is not about one giant computer, but a large batch of infrastructure: hundreds of servers, dozens of data storage systems and switches. The main condition is that the equipment must be included in the registry of Russian products.

For a developer this looks like a distant corporate purchase. But such tenders determine what hardware the internal platforms, cloud services and business applications of large companies will run on in a few years. If the set of supported processors, network adapters, disk controllers and management tools is limited by procurement conditions, teams have to take this into account at the architecture and testing stage.

What Exactly Is Being Purchased

The published description lists three main classes of equipment: servers, data storage systems (DSS) and switches. Servers perform computation, storage systems hold data, and switches connect nodes to each other. In a simple analogy with an office: servers are the employees, storage is the archive, and switches are the corridors and doors through which documents move.

The starting price of the tenders approaches 7 billion rubles. This is the upper starting ceiling of the procurement procedures, not confirmation that the customers have already paid suppliers exactly that sum. The final cost can only be determined after the bidding and the selection of winners. That is why a headline such as "will pay 7 billion" should be read with caution: for now it is more accurate to speak of announced purchases with this starting price.

The exact delivery addresses are not disclosed. The source data also does not make it possible to establish specific equipment models, manufacturers, deployment timelines or the split of the budget between servers, storage and the network. Without the tender documentation, it is impossible to confidently assess the performance of the future infrastructure or compare supplier offers.

Why the Registry Changes the Engineering Task

The requirement that equipment be included in the registry of Russian products narrows the range of acceptable solutions. This does not necessarily mean a worse system, but it adds new constraints to a familiar engineering task. It is not enough for a team to check the number of processor cores and the amount of memory. They need to make sure the operating system sees the controllers, drivers work under load, monitoring tools receive the necessary metrics, and firmware and spare components will be available throughout the entire service life.

Imagine a service that was previously run on a typical foreign server platform. Formally, its containers may start on the new hardware without changes. Problems emerge later: the network adapter handles load differently, the monitoring system does not recognize the sensors, and disk subsystem performance differs from lab expectations. Therefore compatibility cannot be confirmed by a single successful installation; load testing, fault-tolerance checks and recovery scenarios are needed.

A large tender is also a test for Russian manufacturers. A place in the registry is not enough: the supplier must deliver batches of hundreds of devices, consistent configurations, documentation, warranty support and replacement of failed components. Operation will show how ready the equipment is for large-scale deployments.

What Teams Should Do Now

Developers of infrastructure products should separate software requirements from dependence on a specific server. It is useful to fix in advance the supported processor architectures, operating system versions, drivers, network requirements and acceptable storage performance. This turns the statement "it must work on Russian hardware" into a verifiable list of conditions.

Product and technical leaders should ask suppliers for test benches or sample units before mass deployment. On them, teams should run real workload profiles, firmware updates, disk failure, loss of network connectivity and restoration from backup. The purchase price attracts attention, but the real cost will show up later, in compatibility, maintenance and engineers' time. For now the tenders give the market scale and a direction of demand, but it is too early to draw conclusions about winners and equipment quality.

Story

Key Questions Answered

What Exactly Is Being Purchased?

The published description lists three main classes of equipment: servers, data storage systems (DSS) and switches. Servers perform computation, storage systems hold data, and switches connect nodes to each other. In a simple analogy with an office: servers are the employees, storage is the archive, and switches are the corridors and doors through which documents move. The starting price of the tenders approaches 7 billion rubles.

Why the Registry Changes the Engineering Task?

The requirement that equipment be included in the registry of Russian products narrows the range of acceptable solutions. This does not necessarily mean a worse system, but it adds new constraints to a familiar engineering task. It is not enough for a team to check the number of processor cores and the amount of memory.

What Teams Should Do Now?

Developers of infrastructure products should separate software requirements from dependence on a specific server. It is useful to fix in advance the supported processor architectures, operating system versions, drivers, network requirements and acceptable storage performance. This turns the statement "it must work on Russian hardware" into a verifiable list of conditions. Product and technical leaders should ask suppliers for test benches or sample units before mass deployment.

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.
✦ Private AI Builders Community · Vibe Club

Ship AI Faster with Founders, Engineers & Weekly Architecture Reviews

Inside Vibe Club (hamidun.com/club) — weekly live masterminds with Zhemal Khamidun, Tech Radar, full LMS access, and 370+ production Claude Code skills.

Join Vibe Club →Explore Hamidun Academy
What do you think?
Loading comments…