The agency responsible for Russia's sweeping internet censorship is now proposing to build a government-controlled VPN - not to loosen restrictions, but to let a select group of tech workers quietly work around them. The proposal, floated by Roskomnadzor deputy head Oleg Terlyakov at a June 8 meeting with IT companies, is a direct admission that the state's aggressive blocking campaign has begun to damage the very industry Russia depends on to develop its domestic digital economy. As first reported by the independent Russian outlet The Bell, developers have found themselves cut off from GitHub, Python repositories, and the design platform Figma - all casualties of a censorship infrastructure that makes no exceptions.
The Problem the Government Built for Itself
For years, Roskomnadzor has treated virtual private networks as a threat to state information control. Dozens of commercial VPN services have been blocked, and since April, Russian internet providers have been legally required to detect and terminate active VPN connections at the network level. The effect on ordinary users was the intention. The effect on software developers was apparently not anticipated - or not cared about until complaints accumulated.
The practical consequences are severe. GitHub is the dominant platform for collaborative software development worldwide. Python's package repositories are essential infrastructure for almost any modern application. Blocking access to these resources does not make Russian developers more secure or the state more sovereign; it simply makes Russian software development slower, more expensive, and increasingly detached from the global ecosystem on which it depends.
Rather than carving out exemptions or easing restrictions on proven commercial tools, Roskomnadzor's answer is to build a centralized state alternative - one designed, controlled, and operated by the very agency doing the blocking. The proposal targets "those who really need it," a phrase that immediately raises the question of who decides who qualifies, and on what terms.
Why Developers Are Treating This as a Surveillance Risk
A VPN works by encrypting a user's traffic and routing it through a remote server before it reaches its destination. For a developer in Moscow trying to reach a GitHub repository, a trustworthy VPN means their traffic passes through a server in a jurisdiction beyond Roskomnadzor's reach - and, crucially, through a provider with no obligation to retain or share connection logs with Russian authorities.
A state-run VPN inverts every one of those protections. If all traffic from participating developers flows through a single government-managed gateway, Roskomnadzor would gain a complete, centralized view of who is connecting to what, when, and for how long. The architecture of such a system is, by design, a surveillance instrument. One source present at the June meeting told The Bell bluntly: "Cutting off Russians from international development tools will be even easier if everyone starts using the same VPN." Another observer raised the risk of international reachability: a state-controlled endpoint could itself be blocked by foreign platforms responding to Russia's broader internet policies.
The concern about a two-tiered internet is equally legitimate. If access to essential foreign resources is rationed through a state gateway, only developers who clear whatever approval process Roskomnadzor establishes will be able to work effectively. That creates dependency on official favor rather than open access - a significant shift in how professional work is structured and monitored.
A Pattern of Control That Cannot Fully Deliver
Russia's internet censorship campaign has a documented structural weakness: the technology it seeks to suppress is fundamentally difficult to eradicate. Russian officials have themselves acknowledged that a complete ban on VPNs is "simply impossible." The protocols underlying modern VPN services - including those that use obfuscation techniques to disguise encrypted traffic as ordinary web browsing - are designed precisely to resist detection and blocking. Roskomnadzor has reportedly gone as far as conducting disruptive attacks against the infrastructure of commercial VPN providers, yet usage inside Russia has continued to grow.
The state VPN proposal does not resolve this contradiction. It sidesteps it by offering a controlled channel to a specific professional class while maintaining pressure on everyone else. The implicit message is that access to the global internet is a privilege to be administered, not a condition of professional function or personal freedom.
For Russia's developer community, the choice being offered is a stark one: accept surveillance as the price of accessing the tools needed to do their jobs, or continue finding workarounds that carry legal risk. Few in the industry appear willing to treat the state's proposal as a genuine solution. When the regulator building the walls offers to sell you a door, the terms of entry deserve scrutiny.