Skip to content
Exmergo logoExmergo
All connectors
SLayer logo

Semantic Layer

SLayer

Available

SLayer by Motley, a semantic layer kept as YAML model files. dex reads your SLayer models natively, authors them as reviewable diffs, and runs the SQL SLayer renders under its own cost guard, with no dbt project needed.

View Dex on GitHubBook a Demo

Why connect SLayer?

SLayer by Motley keeps a semantic layer as YAML model files in your repository. Dex treats it as a first-class semantic layer: it reads your models without opening a SLayer datasource, authors them as reviewable diffs, runs the SQL SLayer renders under its own cost guard, and tells you when the models fall out of sync with the warehouse.

  • 1Point Dex at your SLayer models with no dbt project and no MetricFlow anywhere in the path
  • 2Validate every model file with SLayer's own model class from one pinned release, plus checks for paths, duplicate names, unresolved joins, and unknown keys
  • 3Query governed measures through the PII gate and the cost guard on DuckDB, BigQuery, Snowflake, PostgreSQL, and Redshift
  • 4Keep your warehouse credentials with Dex: SLayer renders SQL as a dry run and never opens a connection of its own

Works with Dex

SLayer connects to the Exmergo products your team already uses.

DexP-1
Exmergo DexExmergoDex
slayer/

+ .dex/config.yml

+ semantics/slayer/models/warehouse/orders.yaml

Agent-native analytics engineering on your SLayer semantic layer.

Learn about Exmergo Dex

How it works

Connecting SLayer to

Exmergo DexExmergo DexSLayer renders · Dex executes
  1. 1

    Point Dex at your SLayer models

    Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo, then add the SLayer extra with pip install 'exmergo-dex-core[slayer]'. Set semantic.vendor: slayer in .dex/config.yml, point semantic.slayer.base_dir at SLayer's storage root, and list your model files under semantic.slayer.models.

    SLayer

    $ /plugin marketplace add exmergo/exmergo-agent-plugins

    $ /plugin install dex@exmergo

    $ pip install 'exmergo-dex-core[slayer]'

  2. 2

    Read the catalog before you touch anything

    /dex:explore loads your SLayer models straight out of the repository and returns the models, columns, joins, and saved measures they declare. Declared primary keys and joins become evidence Dex uses when it profiles tables and verifies joins.

    SLayer

    $ /dex:explore

  3. 3

    Author models as reviewable diffs

    /dex:transform writes and updates your SLayer model files through semantic slayer define, and transform apply commits them. Every file is validated by SLayer's own model class from one pinned release, so what Dex accepts is what SLayer accepts.

    SLayer

    $ /dex:transform

    $ semantic slayer define

    $ transform apply

  4. 4

    SLayer renders, Dex executes

    SLayer turns a governed query into SQL as a dry run and never touches your warehouse. Dex runs that SQL through its own connector, behind the PII gate and the cost guard, so a semantic query spends no more than any other query Dex runs.

  5. 5

    Catch drift automatically

    /dex:maintain snapshots your SLayer layer and runs SLayer's own schema checks against the warehouse: a declared column that disappeared, a column whose type changed, a table that no longer exists.

    SLayer

    $ /dex:maintain