Yes, Apache Iceberg is actually open. The more useful question is what part of your Iceberg architecture is open after a vendor wraps it.

The direct answer

Apache Iceberg is an Apache Software Foundation project. It is released under the Apache License 2.0, has a public specification, and is developed through Apache project governance. That is a strong openness story at the table-format layer.

So yes, Iceberg itself is open source and openly specified. That does not mean every product that says "Iceberg" gives you open control of the whole architecture.

The catalog caveat is where buyers get surprised

Iceberg tables need catalogs. The catalog coordinates identifiers, metadata locations, and table operations. If the catalog is private, the governance model is private, or critical metadata cannot leave a managed service, the architecture may still create lock-in around an open table format.

This is the buyer trap. Open table format, closed control plane. Same movie, better soundtrack.

Core idea: Iceberg can be open while your Iceberg implementation is not open enough.

What openness should prove

A credible Iceberg implementation should let compatible engines read the table, expose table metadata through documented behavior, support a clear catalog strategy, and make governance understandable outside one vendor UI.

Open does not mean every engine can safely write every table in every situation. It means the contract is visible, implementable, and not dependent on secret platform behavior.

Questions to ask

  • Which Iceberg spec version and features are supported?
  • Which catalog owns table operations?
  • Can another engine read the table without a custom export?
  • Can metadata, policies, and lineage survive if the managed service changes?

Iceberg gives you a real open foundation. You still have to make sure nobody builds a locked room on top of it.

Sources to start with

These are the primary sources I would start from when checking the claims in this piece.