Open Data Infrastructure
Who Actually Governs Apache Iceberg?
Iceberg is "open" because it lives under Apache governance. That governance model is the real portability guarantee, not the marketing.
Open source is not a license stamp. It is a governance model that determines who can steer the road map and who can block the exit.
The governance question buyers ignore
When teams say they want "open table formats," they often mean "we can read the files." That is table-stakes.
The governance question is harder and more important: who controls the specification, the project direction, and the release process when competing vendors disagree?
Core idea: interoperability survives conflict only when governance is neutral.
How Apache governance works
Apache projects are governed under the Apache Software Foundation. At a high level, projects are managed by a Project Management Committee (PMC) with committers who have earned that role through contribution and community trust.
This matters because it is an institutional constraint on capture. A single company can contribute heavily, but it cannot unilaterally rewrite the rules of the project the way it can for a vendor-owned "open" repository.
What that means for Iceberg
Apache Iceberg is an ASF project, with an open specification and an open community process. That does not mean every outcome is guaranteed. It means the process has a real governance backbone.
For ODI, that is the point. You can build a portability strategy on an open spec only if the spec is governed in a way that can outlast corporate incentives.
Signals to look for
If you are evaluating "open" data infrastructure components, ask questions that reveal governance reality.
- Is the specification published openly and versioned?
- Is there a visible PMC and contributor community?
- Do multiple organizations contribute meaningfully, or is it a single-vendor repo with a veneer of openness?
- Are releases and road map decisions documented in public?
- Does the project have a neutral foundation and a real community process?
If the answers are unclear, treat the component as vendor-controlled infrastructure. That changes the risk profile immediately.
Sources to start with
Start with ASF governance basics, then read Iceberg's community documentation and spec.