Open Data Infrastructure
The Risk of Single-Vendor "Open" Projects
Open source is not a brand. If one company controls governance, road map, and distribution, your portability plan is already compromised.
A project can be "open" and still be a trap. The license tells you what you can do with the code. It does not tell you who controls the future.
Why single-vendor control matters
If one company controls governance, it can steer the project in ways that maximize its product advantage. Sometimes that is done intentionally. Sometimes it is simply the result of incentives. Either way, the outcome for a buyer is the same: your "open" dependency behaves like a vendor dependency.
Core idea: portability is a governance property as much as a technical property.
Common open-washing patterns
Most open-washing is not blatant. It is structural.
- Trademark gatekeeping: the code is open, but the official distribution is tightly controlled.
- Road map opacity: major decisions happen in private, and the public repo receives the output later.
- Contribution illusion: many stars and forks, but few meaningful external committers.
- Compatibility by adapter: the "open" layer exists, but real behavior requires proprietary extensions.
Questions buyers should ask
If you are buying a product built on an "open project," ask questions that reveal control.
- Who controls governance and release rights?
- Can independent contributors become maintainers?
- Is the specification separate from the implementation?
- Can you run the core functionality without the vendor-managed control plane?
- What does an exit look like in weeks, dollars, and metadata loss?
An ODI playbook
The ODI approach is simple, but it is not easy. You must prefer neutral governance and open contracts at the boundaries.
- Anchor data portability on open table formats and open catalog interfaces.
- Prefer standards and specs that are governed under neutral foundations.
- Continuously test multi-engine interoperability for the workflows that matter.
- Design your exit path as part of the architecture, not as a contingency plan.
If you want to be able to leave, you must build as if you will.
Sources to start with
Start with the definition of open source and the governance models that make openness durable.