Plexara
The asset is the metadata
The data was always yours. It sits in your warehouse, your object storage, your operational databases. What a data platform adds on top is meaning: the description that says what a column actually holds, the glossary term that fixes a business definition, the lineage that traces a number back to its source, the tag that marks a field as sensitive.
That layer of meaning is the thing that accumulates. On Plexara it accumulates as a byproduct of use, because documentation happens while people work rather than in a separate cataloging project. Over months it becomes the most valuable and most expensive-to-recreate part of the deployment.
So the real lock-in question is not about the data. It is about that layer of meaning. If it is captive, leaving means re-authoring everything your team explained. If it is portable, leaving costs you nothing but the platform itself.
What gets written down
Descriptions
What a table or column actually means
Glossary terms
The business vocabulary your team agreed on
Lineage
How data flows from source to report
Tags & classifications
PII, sensitivity, domain ownership
Ownership
Who is accountable for each dataset
Data contracts
The shape and guarantees a dataset promises
Open formats decide it
Metadata authored through Plexara is stored in DataHub, modeled as entities, aspects, and relationships in an open, documented schema. DataHub is open source under a permissive license. The catalog is readable by anything that speaks the schema, not only by the platform that wrote it.
Lineage is the same story. When provenance is emitted to an open specification rather than written into a private log, the graph of how data flows stays usable in any tool that reads the spec. The record of how a report was built does not evaporate when the tool that recorded it goes away.
This is why the format matters more than the promise. A vendor can pledge that you will never want to leave. Only an open storage format can guarantee that leaving is cheap, because the guarantee lives in the data structure, not in the relationship.
Where the metadata sits
Closed catalog
Captive in a proprietary store
- Definitions and lineage held in a vendor-specific format
- Export is partial, lossy, or gated behind the contract
- Leaving the product means re-authoring the documentation
- The switching cost points back at the vendor
DataHub, open schema
Stored in open formats
- Entities, aspects, and relationships in a documented schema
- Lineage emitted to an open specification, not a private log
- The catalog is readable without the platform that wrote it
- What your team authored stays yours
Where it lives, and why that is deliberate
Plexara is the layer that captures meaning during a conversation and the governance that decides who can see what. It is not the store of record for your metadata. The store of record is DataHub, in open formats, and that separation is on purpose.
It is the same reasoning behind building on protocols rather than products. The orchestration and governance layer can evolve, or be replaced, without holding the catalog hostage. The metadata sits underneath it in a format that does not depend on it.
Regulators have encoded the same principle for personal data: the right to receive it in a structured, machine-readable format and move it elsewhere without hindrance. The instinct is sound well beyond its legal scope. Information you authored should be information you can take with you.
Plexara writes, DataHub holds
Plexara
captures meaning in use
DataHub
entities · aspects · relationships
open schema, Apache-2.0
Portability is a property, not a promise
Keeping what you authored should not require staying. When the catalog, the lineage, and the definitions live in open formats, continuing with a platform becomes a decision about the value it delivers, not a decision forced by the cost of extraction.
That is the standard worth holding any data platform to. Not whether it has an export button, but whether the thing it stores is already in a form you could read without it.
Further Reading
The Metadata Model
DataHub Project · 2026
DataHub models all metadata as entities, aspects, and relationships using an open, documented schema language (PDL). DataHub is open source under the Apache License 2.0, so metadata is stored in a portable format rather than a proprietary one.
OpenLineage Object Model
OpenLineage project (The Linux Foundation) · 2026
An open specification for collecting data lineage as standardized run, job, and dataset events across tools. Because lineage is emitted to an open spec rather than locked inside one vendor, the provenance graph remains usable after a platform change.
Art. 20 GDPR: Right to data portability
European Union (Regulation (EU) 2016/679) · 2016
Grants the right to receive personal data in a structured, commonly used, and machine-readable format and to transmit it to another controller without hindrance. A recognized governance analogue for the principle that data should be portable, not captive.