A museum director in Central Africa discovers with dismay that their database is no longer accessible. The annual subscription to the Western collections management software was not renewed due to budget cuts. When they ask to retrieve the data their team spent five years entering, customer support replies that an export in Excel or JSON format is only available with the "Premium" package, billed at several thousand euros. The museum is paralyzed.
This nightmarish situation is the perfect illustration of Vendor Lock-in. It is one of the most devastating traps of digital transformation, and it directly threatens the heritage sovereignty of countries in the Global South.
1. What is Vendor Lock-in?
Vendor Lock-in refers to a situation where a customer (here, a museum or a ministry of culture) becomes so dependent on a technology provider (the vendor) that they can no longer change systems without incurring prohibitive financial, technical, or human costs.
In the museum sector, this lock-in often takes the form of proprietary CMS (Content Management Systems). Companies design beautiful cataloging software that is very easy to use. Institutions, seduced by polished sales demonstrations or subsidized by international NGOs, sign up.
But the trap closes on three levels:
A. Data Format Lock-in
Proprietary software often saves your metadata (descriptions, provenance, materials) in encrypted or obscure formats. If you decide to leave the software ten years later, the export gives you a file unreadable by any other system. Your data has become hostage.
B. Platform Lock-in
The software is hosted on the provider's "Cloud." You do not have direct access to your database. If the company goes bankrupt, changes its prices by 300%, or decides to stop operating on the African continent, your institution collapses with it.
C. API Lock-in
You want to connect your database to a new tourist application or an interactive touch screen in the museum lobby. The proprietary software does not offer an open API (Application Programming Interface), or charges a premium for each external connection, killing local innovation in the bud.
2. The Hidden Cost of "Free" and Subsidies
Vendor Lock-in strikes particularly hard in Africa because of the dynamics of international funding.
When a Western donor finances a digitization project, they often impose or strongly recommend using their own country's software solution. The first year of use is "offered" or covered by the grant. The African institution enters thousands of inventory records into this system.
Three years later, the grant project ends. The African museum is left alone to pay the annual license costs (which are indexed to European or American economies, not an African ministry's budget). Unable to pay, the museum is disconnected. The digitization work is blocked. It is digital colonialism in its most bureaucratic form.
3. The Ibeji Systems Solution: Open Source and Open Standards
To break this cycle of dependency, Ibeji Systems advocates for and builds its architectures around the Open Source philosophy and Open Standards. The goal is not to tie institutions to our technologies, but to liberate them.
Open Source as a Guarantee of Portability
When we deploy the Meridian Archive operating system on a Sovereign Node, we use Open Source technological building blocks (for example, PostgreSQL databases or Elasticsearch search engines).
The source code is not a secret black box. If, in ten years, a museum decides to no longer work with the Ibeji Systems agency, its IT department can take the code, audit it, modify it, and continue to run the database. The institution does not need our permission to continue to exist digitally. This is the true definition of data sovereignty.
Strict Adherence to Global Standards (IIIF and JSON-LD)
To avoid data format lock-in, we structure each archive according to non-proprietary international standards.
- For high-definition images, we use the IIIF (International Image Interoperability Framework) standard. It's not our format; it's the global standard for the Semantic Web.
- For textual metadata, we use the JSON-LD format. Any junior developer, anywhere in the world, knows how to read and extract data from a JSON file.
Open APIs by Default (API-First Design)
Ibeji Systems's architecture separates the engine (the database) from the bodywork (the visual interface). The engine communicates with the bodywork via an open API. This means that a museum can invite a local video game development or mobile app startup to connect directly to the collections database to create new experiences, without ever needing Ibeji Systems's permission. The digital ecosystem remains open and fertile.
Conclusion: Independence is Written into Contract Clauses
Before signing a contract with a museum software provider, curators and institution directors must ask three relentless questions, well before swooning over the beauty of the interface:
- How can I retrieve all of my raw data if I cancel the contract tomorrow?
- In what exact format will my data be exported (standard or proprietary file)?
- Do I own the code that runs my database, or is it merely rented to me?
Adopting Open Source and open standards sometimes requires a steeper technical learning curve at the beginning (that famous "friction" necessary for freedom). But it is the only bulwark against digital hostage-taking. The memory of a continent must never be locked behind a third-party company's paywall.
Discover how Ibeji Systems helps you regain control: