# Lock-in moved to the catalog: how to keep your data platform portable

> Open table formats such as Delta Lake and Apache Iceberg made data files portable, but lock-in moved up a layer: to the catalog, governance policies, pipelines and semantic models. To stay portable, use an open REST catalog protocol, keep policies and lineage exportable, write pipelines in open tools such as dbt and Spark, and keep a tested exit plan.

Source: https://datanature.ai/blog/avoid-data-platform-lock-in-catalog-layer
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

## Didn't open formats solve lock-in?

Partly. Parquet files in Delta or Iceberg format can be read by many engines. But practitioners and analysts point out that switching cost now sits in the catalog, access policies, workflow definitions, notebooks and semantic models tied to one vendor.

## Where does lock-in hide today?

- **Catalog:** table registrations, permissions and lineage in a proprietary service
- **Governance policies:** row and column rules written in one vendor's syntax
- **Pipelines:** jobs defined in a vendor-specific workflow tool
- **Semantic layer and BI models:** KPIs defined inside one tool
- **Identity:** cloud IAM roles and grants
- **Contracts:** committed spend that makes moving expensive

## How do you stay portable?

1. **Use open formats natively.** DataNature supports both Delta and Iceberg.
2. **Prefer the Iceberg REST catalog protocol** so other engines can read and write.
3. **Keep policies and lineage exportable** in documented formats.
4. **Write transformations in dbt, SQL and Spark,** not proprietary workflow languages.
5. **Define KPIs once** in a semantic layer that serves several BI tools.
6. **Test an exit once a year:** read your tables from a second engine.

## How does DataNature approach this?

Tables are open Delta and Iceberg in your storage. Pipelines use Spark, SQL and dbt. Atlas metadata stays inside your deployment. You can run DataNature in your own cloud account or data centre, so the infrastructure is yours too. See [Iceberg vs Delta Lake](/blog/iceberg-vs-delta-lake).

## How does DataNature keep the catalog portable?

Data sits in Apache Iceberg tables, readable by any Iceberg engine. Transformations live as dbt models in your own Git repository, not inside the platform. Semantic models are YAML files in the same repository. Lineage comes from dbt artifacts committed with the code, and where installed the catalog is based on DataHub, an open-source metadata platform. Policies are defined per engine in [Atlas](/platform/atlas) and documented, so they can be recreated elsewhere. Leaving would mean redeploying engines, not unlocking data.

## How does DataNature Atlas keep this secure and compliant?

Governance is part of the architecture, not a separate tool bolted on later. [DataNature Atlas](/platform/atlas) is the platform's governance module:

- **Knows your data**: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- **Controls access**: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- **Governs AI**: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- **Proves it**: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- **Stays local**: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read [DataNature Atlas in depth](/blog/datanature-atlas-governance-rbac-abac-pii-masking) or see [security and compliance](/security).
