Roskomnadzor, the Russian federal agency responsible for blocking hundreds of foreign websites and systematically dismantling access to VPN services, is now proposing to build one of its own. The plan, revealed at a June 8 meeting between the regulator's deputy head, Oleg Terlyakov, and several Russian IT companies, would create a government-controlled VPN designed to give the country's software developers access to foreign platforms they can no longer reach. The catalyst is a problem entirely of the state's own making: its aggressive censorship apparatus has cut off developers from GitHub, Python package repositories, and design tools like Figma - resources on which modern software development depends.
When the Censor Becomes the Gatekeeper
The proposal was first reported by The Bell, an independent Russian news outlet, following a wave of complaints from developers who described being effectively locked out of the global technology infrastructure. Their frustration is understandable. GitHub is not merely a place to share code - it is the central nervous system of collaborative software development worldwide. Python's repositories distribute the packages that power everything from data science to backend systems. Blocking these platforms does not harden Russia's digital borders; it degrades the productivity and competitiveness of the very tech sector the state has repeatedly identified as strategically critical.
Rather than acknowledging the contradiction by easing restrictions, Roskomnadzor's response is to offer a controlled exception. The proposed state VPN would be available to "those who really need it" - a phrase that, in the context of a tightly supervised regulatory environment, carries unmistakable undertones of selectivity and conditionality. Access to the open internet, in other words, would become a privilege granted and managed by the same body responsible for restricting it.
The Surveillance Problem Hidden Inside the Solution
Developers and industry insiders who attended the June 8 meeting were not reassured. Several described the proposal as "shady," and their skepticism is technically well-founded. A VPN works by routing a user's traffic through a server - encrypting it in transit and masking its origin - before it reaches its destination. When that server is operated by a private, independently audited company with a verified no-logs policy, it provides meaningful protection. When the server is controlled by a government regulator with a documented interest in surveillance, the architecture inverts entirely: rather than shielding user activity, it centralizes visibility over it.
Routing all Russian developer traffic through a single state-managed gateway would give Roskomnadzor a comprehensive, real-time window into which platforms developers access, how often, and for how long. One source present at the meeting told The Bell: "Cutting off Russians from international development tools will be even easier if everyone starts using the same VPN." The concern is precise. Concentration of traffic through one choke point does not solve the censorship problem - it simply moves the chokepoint closer to the user, while adding a layer of institutional oversight that previously did not exist.
There are also international dimensions to consider. A centralized state VPN with fixed infrastructure could itself become a target for external blocking. Foreign platforms wary of serving Russian state-controlled endpoints might restrict access, potentially worsening the very access problem the scheme is meant to address.
A Contradiction Years in the Making
Russia's attempt to assert sovereign control over its digital space has been building for years. Roskomnadzor has blocked access to major VPN providers, and since April, Russian internet service providers have been legally required to detect and block active VPN connections at the network level - a significant technical escalation. There have also been credible reports that the regulator pursued more aggressive tactics, including what appeared to be distributed denial-of-service attacks against VPN infrastructure. Yet despite this sustained campaign, Russian officials have themselves acknowledged that eliminating VPN use entirely is "simply impossible." Encryption is not a loophole; it is a mathematical property. No regulatory decree can outlaw it in practice.
What the state VPN proposal reveals, then, is not a new strategy but the exhaustion of old ones. Faced with a technology it cannot suppress and an industrial sector it cannot afford to cripple, Roskomnadzor has arrived at a compromise that satisfies neither goal cleanly. It will not restore genuine internet freedom for developers, and it will not improve Russia's standing as a destination for global tech investment. What it will do, if implemented, is extend the state's surveillance infrastructure into a professional community that has, until now, maintained some practical distance from it.
A Two-Tiered Internet With All the Wrong Incentives
Critics of the proposal have raised a longer-term concern that goes beyond surveillance: the risk of institutional stratification. If access to essential foreign tools is mediated through a system that requires government approval, a structural divide emerges between those granted access and those who are not. As one source from a Russian IT association put it to The Bell, "a privileged caste with full access will emerge." That dynamic - where professional capability depends on proximity to state favor - is corrosive to exactly the kind of independent, innovative engineering culture a technology sector requires to function.
For Russia's developers, the choice being offered is not between restriction and freedom. It is between two forms of restriction: one that is blunt and external, and one that is precise and internal. Neither is a solution. A genuine one would require the state to confront the fundamental incompatibility between an informationally closed political environment and a technologically competitive economy - a confrontation that, so far, it shows no sign of being willing to have.
