Russian Organizations Allocate 4.5 Trillion Rubles to Innovation Spending in 2025
Large and medium-sized Russian organizations spent 4.5 trillion rubles on innovation in 2025. Almost half of the total came from the services sector, while information technology and telecommunications accounted for 860.9 billion rubles.
The calculations were released by the Institute for Statistical Studies and Economics of Knowledge at HSE University using data from Rosstat. Innovation intensity, measured as the ratio of spending to shipped output, reached 2.7 percent, exceeding the corresponding figures for Finland, France, and Austria cited in the study.
The entire services sector allocated roughly 2.3 trillion rubles to innovation. Of this amount, 882.7 billion rubles went to scientific research and development, and 860.9 billion rubles were directed specifically at telecommunications and information technologies.
Inside an IT Company
IR Director Vladislav Anshakov of Astra Group described how such investments materialize in practice. The primary expense is the creation and enhancement of products; the group maintains a portfolio of more than 37 solutions and services, including Astra Linux, database management systems, and backup solutions.
The second major area covers equipment for cloud infrastructure and artificial intelligence. Anshakov noted that computing capacity represents one of the most capital-intensive investments in the sector.
The third direction involves acquiring ready-made technologies and development teams. In 2026 the group obtained exclusive rights to the intellectual property of the Perseus DBMS and integrated around 50 of its developers. It also purchased a 26 percent stake in AI developer AIB.
Nevertheless, such large-scale investment remains inaccessible to many organizations. According to HSE University data, more than one-third of companies view the high cost of innovations and the lack of their own funds as serious constraints.
Related articles
Building Your First Home Network Lab: Essential Tools and Experiments to Understand Corporate Networks
A cybersecurity professional without network knowledge resembles a guard without a building blueprint, spotting alarms but unable to trace the intruder. Setting up a personal lab on a standard computer bridges this gap through virtualization and hands-on practice with protocols and attacks. The guide recommends GNS3 for topology emulation, VirtualBox or VMware for running Windows and Linux workstations, Cisco Packet Tracer for quick simulations, Wireshark for traffic analysis, and draw.io for diagramming. Key experiments include configuring Cisco IOS routers with IP addressing, testing default gateways, observing ARP requests and replies, triggering broadcast storms via switch loops, and enabling STP to prevent loops. The lab demonstrates how legacy protocols like ARP expose networks to spoofing and why segmentation with VLANs and firewalls matters. Resources from CyberED provide demo access to courses on SOC analysis, penetration testing, and AI applications in security to extend learning.
PSLC and Agent-Ops: From Product Support to Infrastructure Transformation
Sergey Zhitinsky, founder of Git in Sky, attended the OPS Talk by Sber meetup on October 19 and discussed the PSLC methodology with architect Alexander Shapovalov. PSLC, or Product Service Lifecycle, outlines two loops for restoring services immediately and improving reliability to prevent recurrence through teams, knowledge, and platform support. Agent-Ops focuses on eight detailed steps for individual infrastructure tasks: intention, evidence collection, diagnostics, planning, approval, controlled change, verification, and lessons learned. The article illustrates their complementary use in a scenario where post-release log growth fills a database disk, requiring both service restoration and root-cause fixes. Both approaches emphasize knowledge retention, action control, and human accountability, though Agent-Ops v0.5.1 mandates explicit human approval and separate execution for production changes. PSLC suits larger organizations with shared platforms, while Agent-Ops targets smaller teams handling infrastructure operations with AI agents.
Telegram macOS Developer Says 99.9% of Client Code Is Now Written by AI and Suggests Firing Manual Coders
Mike, the developer of the official Telegram client for macOS, stated that artificial intelligence now generates 99.9 percent of the messenger's client code. He argued that programmers who continue writing code manually should be dismissed. In a Telegram discussion, Mike cited the gram.org website as an example created entirely with AI assistance in a single day, with domain support from Pavel Durov. He also described adapting the iOS client for a foldable iPhone Duo overnight using Claude. According to Mike, even designers are now contributing to client code, and 80 to 90 percent of Telegram developers share his positive view of AI tools. When participants raised questions about code quality and security, Mike replied that AI also identifies and fixes vulnerabilities, claiming the resulting code is superior to human-written equivalents. He further announced plans to open a new GitHub repository for the macOS client source code, as the previous repository had not been updated for over a year.
Secure Boot on Arch Linux: Enabling Protection for UKI Without Replacing Factory Keys
A detailed guide explains how to configure Secure Boot on Arch Linux for Unified Kernel Images without replacing the motherboard's factory keys or relying on Microsoft certificates. The author chose the minimal-intervention approach of adding a custom key to the existing DB section via the UEFI interface instead of using sbctl enroll-keys or shim. The process begins with backing up existing keys to a FAT-formatted USB drive directly from the BIOS menu. New keys are then generated using sbsigntools and openssl, converted to DER format, and enrolled through the ASUS Prime 790-P UEFI interface. A post-hook script for mkinitcpio automatically signs the UKI after every kernel update, ensuring the entire unified image remains protected. The method preserves the original Microsoft and vendor certificates while adding only the user's own signing key.