Skip to content

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.

← All connectors
  • Semantic layer
  • Note:
  • Catalog-first · local deployment

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.

What you get
  1. 1Keep metric, dimension, and relationship definitions in a vendor-neutral Apache standard instead of one vendor's proprietary format
  2. 2Point Dex at your Ossie documents with no dbt project and no MetricFlow anywhere in the path
  3. 3Turn declared primary keys, unique keys, and relationships into evidence Dex uses when it profiles tables and verifies joins
  4. 4Author and update documents as reviewable diffs, written byte-for-byte so your comments, quoting, and ordering survive untouched
In your repositoryDex

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. 1

    Point Dex at your Ossie documents

    Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo, then add the Ossie extra with pip install 'exmergo-dex-core[ossie]'. Set semantic.vendor: ossie in .dex/config.yml and list your documents under semantic.ossie.files.

    ossie
    • /plugin marketplace add exmergo/exmergo-agent-plugins
    • /plugin install dex@exmergo
    • pip install 'exmergo-dex-core[ossie]'
  2. 2

    Read the catalog before you touch anything

    /dex:explore loads 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. 3

    Author documents as reviewable diffs

    /dex:transform writes and updates your Ossie documents through semantic ossie define, and transform apply commits them byte-for-byte, so your comments, quoting, and ordering survive untouched.

    ossie
    • /dex:transform
    • semantic ossie define
    • transform apply
  4. 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. 5

    Catch drift automatically

    /dex:maintain snapshots 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.

Waitlist

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.

Join the connector waitlist