# vendor lock-in Vendor lock-in is a situation in which a customer cannot easily transition from a product or service to a competitor, often because of proprietary technologies or incompatibility. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend DevFeed: [Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend]() Original publisher: [Read original article]() Author: Gabriele Bartolini (EnterpriseDB) and CNCF Ambassador, Rob Kenefeck (ControlPlane) Published: 2026-09-16T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [CloudNativePG](), [Kubernetes](), [PostgreSQL](), [Open Source](), [vendor lock-in]() Tags: [blog](), [cloudnativepg](), [docker](), [hashicorp-vault](), [helm](), [infrastructure](), [kubernetes](), [linux-foundation](), [open-source](), [postgresql](), [secrets](), [vendor-lock-in]() ### AI overview A tutorial describes deploying OpenBao on Kubernetes with a three-instance CloudNativePG PostgreSQL cluster as its storage backend. It explains certificate-based authentication and a local Kind-based test environment. ### Source excerpt Managing infrastructure secrets on Kubernetes needs a backend that is self-healing and free of vendor lock-in, and that is exactly what OpenBao (the Linux Foundation's open-source fork of HashiCorp Vault) and CloudNativePG give you: an entirely... ## What is bring your own LLM (BYO LLM)? DevFeed: [What is bring your own LLM (BYO LLM)?]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Large Language Model](), [vendor lock-in](), [Artificial Intelligence]() Tags: [agents](), [industry-insights](), [integration](), [large-language-model](), [llm](), [platforms](), [vendor-lock-in]() ### AI overview The article explains bring your own LLM (BYO LLM), an architecture that lets organizations choose and change the large language model powering their AI agents. It describes how Twilio's Agent Connect mediates between selected models and communication channels, preserving context while separating model ownership from platform-provided voice, messaging, streaming, identity, and escalation capabilities. ### Source excerpt Bring your own LLM (BYO LLM) lets you choose the large language model powering your AI agents rather than accepting whatever your platform ships with. ## Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in DevFeed: [Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in]() Original publisher: [Read original article]() Author: Robert Bernier Published: 2026-08-26T14:07:50Z Content type: opinion Language: en Sources: [Blog - Percona]() Topics: [PostgreSQL](), [vendor lock-in](), [Database Migration](), [Open Source]() Tags: [database-migration](), [database-trends](), [insight-for-dbas](), [insight-for-developers](), [migration](), [open-source](), [postgres](), [postgresql](), [vendor-lock-in]() ### AI overview The article examines how commercial ecosystems built around PostgreSQL can create walled-garden effects and constrain the portability of PostgreSQL-compatible systems. It highlights migration complexity, switching costs, and potential data-integrity risks when leaving such ecosystems. ### Source excerpt These days there's been a lot of talk about Postgres having an impact on "everything". Whether it's replacing legacy systems, creating a new greenfield project or even implementing it as a back-end to an agentic AI, Postgres is today's poster child for innovation. So performing something as dull and straightforward as a database migration should ... Continued The post Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in appeared first on Percona. ## OpenTelemetry Has Graduated... Now what? DevFeed: [OpenTelemetry Has Graduated... Now what?]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-15T18:59:02Z Content type: opinion Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [telemetry](), [Open Source](), [vendor lock-in](), [Instrumentation](), [Traces]() Tags: [cncf](), [instrumentation](), [open-source](), [opentelemetry](), [telemetry](), [traces](), [tracing](), [vendor-lock-in]() ### AI overview This article discusses OpenTelemetry's CNCF graduated status, its history as a unified standard for traces, logs, and metrics, and the role of standardized APIs, language implementations, and the Collector in reducing vendor lock-in. ### Source excerpt In case you missed it: OpenTelemetry (OTel) has officially achieved CNCF graduated status! It now stands proudly alongside amazing open source projects such as Kubernetes and Prometheus, to name just a few. It's been a long journey, and we're very excited... But, now what? To understand where we're going, it's important to understand where we came from. History In the not-so-distant past, telemetry signals were not standardized. This meant telemetry formats differed from tool to tool, with each telemetry vendor creating and maintaining its own instrumentation libraries. Vendor lock-in was a huge problem: If you wanted to switch vendors, you had to strip out the previous vendor's libraries from your code and replace them with the new vendor's libraries. As a result, switching vendors was a nontrivial task. ## Keycloak experimental AuthZEN Support DevFeed: [Keycloak experimental AuthZEN Support]() Original publisher: [Read original article]() Author: Ryan Emerson Published: 2026-05-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [openid](), [API](), [REST API](), [interoperability](), [vendor lock-in]() Tags: [authentication](), [changes](), [idm](), [interoperability](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [release](), [resource](), [rest-api](), [saml](), [sdks](), [sso](), [vendor-lock-in](), [works]() ### AI overview Keycloak announces experimental support for the OpenID AuthZEN Authorization API 1.0 specification starting with version 26.7.0. The feature lets Keycloak act as a Policy Decision Point and expose existing authorization policies through a standardized API for Policy Enforcement Points. ### Source excerpt We are excited to announce that from 26.7.0, Keycloak will include experimental support for the OpenID AuthZEN Authorization API 1.0 specification. This allows Keycloak to act as a Policy Decision Point (PDP), exposing its authorization capabilities through a standardized API that any Policy Enforcement Point (PEP) can consume. You can try this now with the Keycloak nightly release. Why AuthZEN? Authorization has long been fragmented, with competing systems defining their own protocols for answering the same fundamental question: "Can this subject perform this action on this resource?". This means applications are tightly coupled to whichever authorization backend they choose, and swapping providers requires rewriting integration code. AuthZEN changes this by defining a single, vendor-neutral API between the component that asks (the PEP) and the component that decides (the PDP). It is, in many ways, what OpenID Connect did for authentication -- but for authorization. With AuthZEN: No more vendor lock-in -- your application speaks one API regardless of the PDP behind it. RBAC, ABAC, and ReBAC under one roof -- different policy models can answer the same request format, enabling true interoperability across authorization paradigms. Centralized, externalized authorization -- policy logic lives in the PDP, not scattered across application code, making it easier to audit and update. Simpler integration -- a clean REST API with a minimal request/response model replaces complex, implementation-specific SDKs. A growing ecosystem OpenID AuthZEN Interop demonstrates that over a dozen independently-developed PDPs can be used interchangeably by the same PEP without changing a single line of application code. By adding AuthZEN support, Keycloak joins this ecosystem and lets you leverage your existing Keycloak policies through the same standardized API used by every other AuthZEN-compatible PDP. How it works The interaction between your application and Keycloak follows the standard PE ## Supabase Template is Now Available on DigitalOcean App Platform DevFeed: [Supabase Template is Now Available on DigitalOcean App Platform]() Original publisher: [Read original article]() Author: Bikram Gupta Published: 2026-02-26T16:43:31Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Supabase](), [Digital Ocean](), [Template](), [backends](), [PostgreSQL](), [Authentication](), [REST API](), [Security](), [Self-hosted](), [vendor lock-in]() Tags: [api](), [authentication](), [backend](), [digitalocean](), [open-source](), [platform](), [postgresql](), [product-updates](), [real-time](), [rest-api](), [sdks](), [security](), [self-hosted](), [storage](), [vendor-lock-in]() ### AI overview DigitalOcean App Platform now offers native Supabase template support. The template deploys a production-ready Supabase backend with managed PostgreSQL, authentication, REST APIs, file storage, and real-time capabilities. ### Source excerpt Modern applications need more than just a database. They need authentication, auto-generated APIs, file storage, and real-time subscriptions. Supabase is a powerful open-source Firebase alternative that transforms PostgreSQL into a complete backend platform. With its developer-friendly SDKs and instant API generation, Supabase is a top request from teams who want full control over their infrastructure without sacrificing speed. Today, we're excited to announce native Supabase template support on DigitalOcean App Platform. Deploy a production-ready Supabase backend with one click, complete with managed PostgreSQL, authentication, REST API, file storage, and real-time capabilities. Benefits Instant Backend: Get authentication, auto-generated REST APIs, file storage, and real-time subscriptions without writing backend code. Production-Ready Security: Every deployment includes JWT authentication, Row Level Security (RLS), and secure credential management out of the box. Self-Hosted Control: Keep your data, auth credentials, and file storage on infrastructure you control--no vendor lock-in. Full-Stack Ready: Deploy Supabase alongside your frontend application in a single App Platform project. Architecture Overview The Supabase template deploys a complete backend stack that auto-generates APIs from your PostgreSQL schema. Your frontend applications connect through four specialized services that handle data, authentication, files, and real-time updates. How Supabase Works Unlike traditional backends where you write API endpoints manually, Supabase auto-generates them from your database schema: Row Level Security (RLS) policies on your tables control who can access what - users only see their own data, automatically. How to Get Started The template repository contains everything you need to deploy Supabase on App Platform: github.com/AppPlatform-Templates/supabase-appplatform You have three deployment paths: One-Click: Use the Deploy to DigitalOcean button in the repository ## Announcing AI for Citizens DevFeed: [Announcing AI for Citizens]() Original publisher: [Read original article]() Published: 2025-07-03T12:00:00Z Content type: news Language: en Sources: [Mistral AI Blog]() Topics: [AI Strategy](), [vendor lock-in](), [Frontier AI](), [AI Platform]() Tags: [ai](), [frontier-ai](), [mistral](), [privacy](), [public-sector](), [vendor-lock-in]() ### AI overview Mistral AI announces AI for Citizens, a collaborative initiative that helps states and public institutions strategically use AI to transform public services, encourage innovation, and maintain competitiveness. The initiative promotes greater control over AI and addresses risks associated with closed systems, vendor dependence, geopolitical constraints, and national requirements for safety, privacy, and data governance. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Using Rails Views, Web Components, React, and Rails ViewComponents Together DevFeed: [Using Rails Views, Web Components, React, and Rails ViewComponents Together]() Original publisher: [Read original article]() Published: 2025-03-03T00:00:00Z Content type: opinion Language: en Sources: [Aha! Engineering Blog]() Topics: [Rails](), [React](), [Web Components](), [Server-side rendering](), [Front end](), [vendor lock-in]() Tags: [components](), [front-end](), [opinion](), [rails](), [react](), [server-side-rendering](), [vendor-lock-in]() ### AI overview The article argues that Rails views, web components, React, and Rails ViewComponents are not mutually exclusive. It explains that each approach addresses different problems and can be combined thoughtfully, including server rendering for simpler data-display features and web components for avoiding vendor lock-in. ### Source excerpt How many times have you heard or read statements like these in tech discussions?"Everything needs to be a single-page app these days. Server-rendered templates are holding you back.""Web components are the future. Why tie yourself to any framework?" ## DynamoDB For System Design Interviews DevFeed: [DynamoDB For System Design Interviews]() Original publisher: [Read original article]() Author: Evan King Published: 2024-11-19T21:30:02Z Content type: tutorial Language: en Sources: [Evan King]() Topics: [DynamoDB](), [Amazon Web Services](), [NoSQL](), [Database](), [Transactions](), [Provisioning](), [Application Development](), [configuration](), [Learning](), [vendor lock-in]() Tags: [aws](), [configuration](), [data-storage](), [database](), [dynamodb](), [learning](), [nosql](), [provisioning](), [system-design-interview](), [transactions]() ### AI overview This tutorial explains DynamoDB for system design interviews. It covers DynamoDB's managed operation, scalability, key-value and NoSQL data model, transaction support, lack of open-source internals, and practical considerations including vendor lock-in and whether interviewers permit its use. ### Source excerpt By the Co-founder of www.hellointerview.comIntro DynamoDB is a fully-managed, highly scalable, key-value service provided by AWS. Cool, buzz-words. But what the hell does that mean and why does it matter? Fully-Managed -- This means that AWS takes care of all the operational aspects of the database. The fully-managed nature allows AWS to handle all operational tasks -- hardware provisioning, configuration, patching, and scaling -- freeing developers to concentrate on application development. Highly Scalable -- DynamoDB can handle massive amounts of data and traffic. It automatically scales up or down to adjust to your application's needs, without any downtime or performance degradation. Key-value -- DynamoDB is a NoSQL database, which means it doesn't use the traditional relational database model. Instead, it uses a key-value model that allows for flexible data storage and retrieval. The moral of the story is that DynamoDB is a super easy to use and can scale to support a wide variety of applications. For system design interviews in particular, it has just about everything you'd ever need from a database. It even supports transactions now! Which neutralizes one of the biggest criticisms of DynamoDB in the past. Importantly, DynamoDB is not open-source, so we can't as easily describe its internals like we did with breakdowns of open source technologies like Kafka and Redis. Instead, we'll focus more on you interact with it. In order to look under the hood, we'll rely on the limited information AWS provides via documentation and the DynamoDB Whitepaper. In this deep dive, we'll break down exactly what you need to know about DynamoDB in order to field any question about it in a system design interview. Along the way, you'll also acquire practical learning that you can later apply in your own projects. Let's break it down! Candidates often ask me, "am I even allowed to use DynamoDB in an interview?"The answer is simple, ask your interviewer! Many will say yes, and just expec ## Planning Your PostgreSQL Migration: Best Practices and Key Considerations DevFeed: [Planning Your PostgreSQL Migration: Best Practices and Key Considerations]() Original publisher: [Read original article]() Author: Ken W. Alger Published: 2024-11-19T19:40:49Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [migration](), [PostgreSQL](), [Database Migration](), [Cloud](), [vendor lock-in](), [interoperability]() Tags: [cli](), [cloud](), [compatibility](), [configuration](), [database](), [database-migration](), [developer-tools](), [heroku-postgres](), [interoperability](), [migration](), [postgresql](), [sql](), [uncategorized](), [vendor-lock-in]() ### AI overview This guide explains how to plan a PostgreSQL migration between cloud providers. It covers evaluating the current database setup, checking PostgreSQL version and extension compatibility, and documenting configuration settings before migration. ### Source excerpt Your organization may have many reasons to move a cloud service from one provider to another. Maybe you've found a better performance-versus-cost balance elsewhere. Maybe you're trying to avoid vendor lock-in. Whatever your reasons, the convenience and general interoperability of cloud services today put you in the driver's seat. You get to piece together the [...] The post Planning Your PostgreSQL Migration: Best Practices and Key Considerations appeared first on Heroku. ## Free the data: Why US federal agencies should standardize on OpenTelemetry DevFeed: [Free the data: Why US federal agencies should standardize on OpenTelemetry]() Original publisher: [Read original article]() Author: Bill Wright Published: 2024-06-26T00:00:00Z Content type: opinion Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [OpenTelemetry](), [telemetry](), [interoperability](), [vendor lock-in](), [Open Source](), [data-processing](), [Monitoring](), [Cloud Native Ecosystem]() Tags: [collection](), [cost-savings](), [government](), [interoperability](), [migrations](), [observability](), [open](), [opentelemetry](), [opentelemetry-data-ingestion-open-source-standards-government](), [public-sector-government](), [standard](), [standards](), [systems](), [telemetry](), [universal-profiling-logs-metrics](), [us](), [vendor-lock-in]() ### AI overview The article argues that US federal agencies should standardize on OpenTelemetry, an open-source observability framework and CNCF project. It presents unified collection of traces, metrics, and logs as a way to reduce vendor lock-in and costs, improve interoperability and collaboration, and provide adaptable monitoring across government applications and infrastructure. ### Source excerpt Adopting OpenTelemetry standards can enhance the government's ability to manage and analyze telemetry data across diverse systems - ensuring consistent and reliable data collection and leading to better decision-making and improved service delivery. ## Data Center Fabric Designs: Size Matters DevFeed: [Data Center Fabric Designs: Size Matters]() Original publisher: [Read original article]() Published: 2024-03-14T07:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [data centers](), [Architecture & Design](), [Networks](), [vendor lock-in](), [Streaming]() Tags: [architecture-design](), [data-center](), [design](), [evpn](), [fabric](), [networks](), [streaming](), [vendor-lock-in]() ### AI overview The article argues that the appropriate data center fabric design depends on network size and operational complexity. Mixing vendors may help large streaming services avoid vendor lock-in, reduce prices, and address supply-chain issues, but it is usually impractical for enterprise data centers because the operational costs of multiple operating systems, support centers, and tooling can outweigh acquisition savings. ### Source excerpt The "should we use the same vendor for fabric spines and leaves?" discussion triggered the expected counterexamples. Here's one: I actually have worked with a few orgs that mix vendors at both spine and leaf layer. Can't take names but they run fairly large streaming services. To me it seems like a play to avoid vendor lock-in, drive price points down and be in front of supply chain issues. As always, one has to keep two things in mind: Read more ... ## The PaaS Dilemma DevFeed: [The PaaS Dilemma]() Original publisher: [Read original article]() Author: Dominic Black Published: 2023-08-03T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [paas and iaas](), [vendor lock-in](), [Open Source](), [hosting](), [Amazon Web Services](), [fly]() Tags: [aws](), [gcp](), [hosting](), [open-source](), [platform-as-a-service-paas](), [vendor-lock-in]() ### AI overview This opinion article discusses how Platform-as-a-Service products create customer trust and vendor lock-in concerns. It compares invisible integrations, illustrated by Fly.io, with deeper integrations such as AWS APIs, and presents an open-source approach as Encore's response to these challenges. ### Source excerpt Overcoming trust issues and vendor lock-in through an open-source approach ## Big Data Storage DevFeed: [Big Data Storage]() Original publisher: [Read original article]() Published: 2022-10-21T17:33:51Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [big-data](), [CSV](), [data](), [Data Infrastructure](), [Compression](), [vendor lock-in]() Tags: [big-data](), [compression](), [csv](), [data](), [data-infrastructure](), [programming](), [storage](), [vendor-lock-in]() ### AI overview This article examines storage and transfer formats for large-scale data. It presents CSV as easy to generate, widely supported, reasonably efficient, compressible, and resistant to vendor lock-in, while noting risks involving dialects, escaping, numeric precision, locale, field ordering, and inconsistent types. ### Source excerpt This is a page about some of the mechanics of 'big data', specifically how to store, transfer and process perhaps 100s of millions or billions of rows/events. Although some people think big data starts at 65k rows, at which point Excel used to lose it, I'm talking about gigabytes of data here. Infrastructure for this kind of thing abounds. Data can however come from lots of sources, and go to lots of different places. ## SaaS vs. Open Core: Comparing Business Models Using S-1 Filings DevFeed: [SaaS vs. Open Core: Comparing Business Models Using S-1 Filings]() Original publisher: [Read original article]() Author: taylor@goteleport.com (Taylor Wakefield) Published: 2019-06-03T00:00:00Z Content type: comparison Language: en Sources: [Teleport]() Topics: [Software as a service](), [Open Source](), [vendor lock-in]() Tags: [comparison](), [open-source](), [saas](), [vendor-lock-in]() ### AI overview This article compares SaaS and Open Core software business models from customer and vendor perspectives. It discusses operational burden, usage-based billing, data control, vendor lock-in, delivery costs, community development, product usage data, and sales and marketing. The supplied evidence says the series concludes by evaluating S-1 filings for an inherent advantage, but it does not provide those results. ### Source excerpt In the final part of this three-part series, we evaluate S-1 filings from SaaS and Open Core companies to determine if either model has an inherent advantage. ## Filling Android Autofill Gaps DevFeed: [Filling Android Autofill Gaps]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-02-13T00:00:00Z Content type: article Language: en Sources: [Artur Dryomov]() Topics: [LineageOS](), [passwords](), [vendor lock-in]() Tags: [android](), [credentials](), [passwords](), [vendor-lock-in]() ### AI overview The article examines Android credential storage and autofill options, including Android Autofill and Google Smart Lock. It discusses the convenience of password managers and cross-device credential access, while noting security concerns with unencrypted backups and vendor lock-in when credentials are stored on Google's servers. ### Source excerpt We can have different opinions but should be able to agree on one thing -- we are humans. Well, except ones who like Gerrit and use Dashboard on macOS. Those are clearly aliens (Mulder was right). All humans tend to forget things. Important and useless, smart and dumb, beautiful and ugly -- it does not matter, any thought or information can disappear. Precious credentials for applications we work on are no exception. ## CloudFormation vs. Terraform DevFeed: [CloudFormation vs. Terraform]() Original publisher: [Read original article]() Author: Wojtek Gawroński (afronski) Published: 2017-04-11T08:00:00Z Content type: comparison Language: en Sources: [Wojtek Gawroński]() Topics: [Terraform](), [AWS CloudFormation](), [Amazon Web Services](), [Infrastructure as code](), [vendor lock-in](), [Disaster Recovery]() Tags: [aws](), [aws-cloudformation](), [c-sharp](), [canvas](), [clojure](), [css](), [css3](), [disaster-recovery](), [erlang](), [html](), [html5](), [infrastructure-as-code](), [javascript](), [mono](), [net](), [node-js](), [sicp](), [terraform](), [vagrant](), [vendor-lock-in](), [webgl]() ### AI overview This comparison examines Terraform and AWS CloudFormation for automating cloud infrastructure. The author explains the decision to use a pure CloudFormation setup, choose AWS, and drop Terraform, while discussing provider dependence, vendor lock-in, and disaster recovery considerations. ### Source excerpt CloudFormation vs. Terraform. a There is a time when every project that uses a cloud computing service has a difficult choice to make - should we automate the infrastructure or not? Immediately after, another question pops up - how should we do it? Should we use a dedicated tool (AWS CloudFormation, Azure Resource Templates, OpenStack Heat or Google Cloud Deployment Manager) or a provider-agnostic solution? And then - immediately after a surprise comes in - at first glance, there is no other tool like Terraform available on the market (but there is - it is called Foreman :wink:). So we have a good tool, built by amazing people (HashiCorp) which does not rely on any particular cloud - problem solved? Not entirely. As a grown up, you know that like the ORM does not let you change database on the fly, Terraform will not let you automatically switch your cloud provider for your entire system. From the other hand - you fear vendor lock-in, and for sure you are considering how to design and prepare disaster recovery scenarios. A lot of unknowns, isn't it? I would like to show my rationale for a new project and infrastructure for which I, among others, was responsible. The motivation which drove us towards a pure CloudFormation setup, the reason behind our bet on AWS, and the motivation behind the decision to drop Terraform. Keep in mind that all remarks and comments pointed in this article are constructive criticism - it does not change my opinion about companies that created those tools at all. I have huge respect for both for AWS and HashiCorp - the work they have done, especially in tooling and cloud computing landscape is outstanding. As a user of AWS Services and HashiCorp tools I am grateful for the work they did. If you do not have experience with CloudFormation or Terraform - please read either amazing documentation or any other introductory article. I will assume your basic knowledge about these two. Terraform is not a silver bullet. When I evaluated Terraform, i ## ReactOS as a second OS in Russian government's software freedom effort DevFeed: [ReactOS as a second OS in Russian government's software freedom effort]() Original publisher: [Read original article]() Published: 2015-06-19T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Open Source](), [Operating system](), [vendor lock-in]() Tags: [free](), [open-source](), [operating-systems](), [os](), [react](), [reactos](), [vendor-lock-in](), [win32](), [winapi]() ### AI overview The ReactOS Foundation submitted ReactOS and the ReactOS-based RosServer to a Russian Ministry of Telecom and Mass Communications initiative seeking independent alternatives to strategically important software. The projects placed second in the operating-system category, behind the ROSA Lab and ALT Linux consortium. ### Source excerpt The Russian Federation along with the BRICS nations are pursuing measures to rid vendor lock-in of strategically important software (http://minsvyaz.ru/en/events/33237/) and substitute such software with free/open software (http://minsvyaz.ru/en/events/32967/). As such an initiative would provide considerable benefits beyond that of any singular agenda, Aleksey Bragin decided to take part in that on behalf of ReactOS Foundation. Since October 2014 he has been a member of the Operating Systems workgroup formed by the Ministry of Telecom and Mass Communications (so-called "