Apache Ossie
Apache Ossie (incubating), the vendor-neutral standard for semantic metadata. Dex reads your .ossie.yaml documents natively and authors them as reviewable diffs, with or without a dbt project.
Why connect Apache Ossie?
Apache Ossie (incubating) is the industry standard for exchanging semantic metadata across analytics, BI, and AI platforms. Dex treats it as a first-class semantic layer: it reads your Ossie documents straight out of the repository, authors them as reviewable diffs, and tells you when they fall out of sync with the warehouse underneath.
- 1Keep metric, dimension, and relationship definitions in a vendor-neutral Apache standard instead of one vendor's proprietary format
- 2Point Dex at your Ossie documents with no dbt project and no MetricFlow anywhere in the path
- 3Turn declared primary keys, unique keys, and relationships into evidence Dex uses when it profiles tables and verifies joins
- 4Author and update documents as reviewable diffs, written byte-for-byte so your comments, quoting, and ordering survive untouched
Agent-native analytics engineering on your Ossie semantic layer.
- .dex/config.yml
- semantics/commerce.ossie.yaml
How it works
Explore, transform, maintain: the Dex loop on Apache Ossie.
- 1
Point Dex at your Ossie documents
Install Dex in Claude Code by running
/plugin marketplace add exmergo/exmergo-agent-pluginsand/plugin install dex@exmergo, then add the Ossie extra withpip install 'exmergo-dex-core[ossie]'. Setsemantic.vendor: ossiein.dex/config.ymland list your documents undersemantic.ossie.files.ossie/plugin marketplace add exmergo/exmergo-agent-plugins/plugin install dex@exmergopip install 'exmergo-dex-core[ossie]'
- 2
Read the catalog before you touch anything
/dex:exploreloads your Ossie documents straight out of the repository and returns the datasets, fields, relationships, and metrics they declare, so the agent works from the layer's own words instead of guessing at your schema.ossie/dex:explore
- 3
Author documents as reviewable diffs
/dex:transformwrites and updates your Ossie documents throughsemantic ossie define, andtransform applycommits them byte-for-byte, so your comments, quoting, and ordering survive untouched.ossie/dex:transformsemantic ossie definetransform apply
- 4
Nothing is written until it validates
Dex checks every prospective document against a content-pinned copy of the Ossie JSON Schema, then against its own integrity rules: unique names, resolvable relationship endpoints, matching key arity. Writes are confined to the paths you configured, and a file that changed after planning refuses the whole edit.
- 5
Catch drift automatically
/dex:maintainsnapshots your Ossie layer and flags it when the warehouse moves underneath it: a source column that disappeared, a declared primary key that stopped being unique, a relationship that no longer resolves.ossie/dex:maintain
Other semantic layers
Dex brings the same loop and the same guardrails to each of these.
Need a connector we don't support yet?
Tell us about your data source and we'll let you know as soon as the connector is available.