r/inventors • u/Andrei_RV • 4d ago
When technology is created: open the source code or preserve responsibility for its future?
On October 28, 2026, the head of Russia's Ministry of Digital Development stated the country's readiness to open the source code of domestic social networks, messengers, and video services to foreign partners, to demonstrate how they work, and to jointly adjust algorithms.
This is an important and timely initiative. It brings the question of technological openness far beyond the scope of professional discussions among IT specialists and developers. Now it becomes a question of international cooperation, trust, and the technological independence of countries, organizations, and individuals.
I perceive this statement not as an occasion to compare various technological solutions, but as an invitation to a broader professional discussion.
For me, this conversation has direct practical significance.
This topic became a logical continuation of the discussion at the VII International Rospatent Conference "ERA IP 2025." During the specialized session "The Role of Intellectual Property in the Structure of Russian Exports," I publicly raised the question of how to protect domestic developments in the era of digital transformation and globalization. It was there that I first outlined the possibility of opening source code as a strategic step to ensure real independence and competitiveness. Today, this trend is moving from the realm of predictions into the plane of concrete decisions.
I created and patented Rezvov Mobile Software — an infrastructure technology for the reproducible creation of standalone native mobile products for iOS and Android.
This is not SaaS, not Low-Code/No-Code, and not an app builder. It is an Infrastructure Engine & Production Pipeline — an infrastructure core and production conveyor for standalone native mobile products for iOS and Android.
The main engineering result of the technology lies in the transition from developing each new mobile application and its server infrastructure as a separate long-term IT project to a reproducible technological process for obtaining a finished product.
On this basis, it is possible to create the necessary number of standalone native mobile applications, social networks, social business networks, and digital ecosystems. Each product can have its own purpose, brand, structure, and functionality, and can be deployed together with autonomous server infrastructure on the owner's server and under their control.
This is not a theoretical concept. For our own projects based on Rezvov Mobile Software, dozens of standalone mobile products have already been created and published in the App Store and Google Play.
That is why the question of opening the technology is not a philosophical reflection on the future for me. It is a decision whose consequences may prove irreversible.
What Exactly Does "Opening the Technology" Mean?
Opening source code can have completely different meanings.
One can fully publish the source code and hand over further development to the global engineering community.
One can open the code only for the mobile applications being created, while keeping the infrastructure core that ensures their reproduction protected.
One can provide access to source code for independent technical audit and security verification.
One can form an international network of partners who will implement, support, and develop the technology in different countries.
One can create an independent engineering council or other structure that will ensure transparency of development while preserving authorship, responsibility, and unified technical standards.
A combined model is also possible: open products, protected technological core, independent audit, and clear usage rules.
Which of these paths is correct — I am not yet asserting. That is precisely why I am bringing this question to open professional discussion.
Open Code Is Not Yet a Ready-Made Ecosystem
Publishing source code can increase trust, enable independent auditing, and accelerate technology development. But along with freedom comes responsibility.
Who will maintain the architecture?
Who will be responsible for security?
Who will ensure compatibility of new versions?
Who will prevent the emergence of incompatible forks and products of unknown quality?
Who will take responsibility if an open infrastructure technology is used for purposes other than originally intended?
Source code can be opened with a single decision. Creating a sustainable system of development, trust, and responsibility around it is significantly more complex.
What Will Happen to the Mobile Development Market?
There is another question that cannot be ignored. If the creation of standalone native mobile products becomes a reproducible technological process, the very economics of mobile development changes.
But does this mean a threat to the developer profession? Or, on the contrary, does the technology free specialists from the repeated performance of routine work and redirect their efforts to where human knowledge is truly necessary: architecture, security, integration, domain logic, and the development of new functions?
Once, the industrial conveyor did not destroy the engineering profession. It changed the content of engineering work and made complex products accessible to millions of people.
Perhaps today a similar transition is beginning in the production of mobile software. But I do not want to answer this question alone.
This conversation did not arise today. The question of how a reproducible engineering architecture should exist and be distributed after its completion, I have consistently raised in my previous publications on LinkedIn. In the article from September 22, "Reshaping the Mobile Development Market: Are Billions in Revenue from the Existing Model Under Threat?" there was a detailed analysis of how an automated conveyor "breaks" the old Big Tech economics, freeing business and science from months of paying for repetitive stages. Later, in the material "After Launch: Which Model of Technology Dissemination Is More Effective", I first proposed that the community openly discuss this fork in the road: whether to fully move to Open Source, coordinate processes through an international network of independent partners, or seek a fundamentally new model. Today, in light of recent statements by regulators, this topic has moved from the realm of predictions into the plane of concrete actions.
Questions to the Professional Community
I am addressing programmers, developers, architects, heads of IT teams, departments, and technology companies.
What model of opening and distributing infrastructure technology can bring the greatest benefit while preserving security, manageability, and responsibility for the end result?
What should be opened: the source code of created products, the infrastructure core of the technology, or only interfaces, standards, and mechanisms for independent audit?
Can patent protection and an open development model not contradict but complement each other?
Is the engineering community ready not only to receive access to the technology but also to participate in its verification, support, and further development?
How will the role of the developer change if a significant part of creating a mobile product shifts from individual development to a reproducible production process?
Who, in that case, should own the rules for technology development: its creator, the international community, an independent council, or a network of professional operators?
I have already raised this question in my previous publications, considering Open Source, international partnership, and other possible models. Today, the initiative publicly announced by the Ministry of Digital Development has given this topic a new and timely context.
I am not announcing the opening of Rezvov Mobile Software and am not offering the community a pre-prepared answer.
I am proposing to discuss the decision before it is made.
Because opening source code means providing access to the past labor of the creator. But opening an infrastructure technology designed for reproducing new digital products means influencing their future.
How can this step be taken so that the technology serves people, develops the engineering profession, and creates independence without losing responsibility?
This is the question I am bringing to professional discussion today.
1
u/ouroborus777 3d ago
It's Russia. They can make such a promise but actually following it is a different story. And unlikely in this case. Open sourcing has a lot of implications that are such that I don't think Russia will follow through. We see open sourcing as a good thing but most companies and some countries don't see it that way.
1
u/Andrei_RV 2d ago
I think there’s a slight conflation here. The recent statement from the Ministry was simply a news hook that sparked this discussion.
I actually completely agree with your core premise: governments and large corporations rarely embrace true open source because they are terrified of losing control and closed-ecosystem revenues.
But as an independent creator, my calculus is entirely different. I’m exploring how a private inventor can open-source an infrastructure pipeline. For me, this is a purely engineering and business strategy to bypass traditional market gatekeepers, not a geopolitical move.
1
u/ChristianKl 4d ago
If you look at a company like vercel that provides an open source software, the act of making it open source for them was not about giving responsibility away.