Dex by Exmergo
Let your agent build your analytics
322 followers
Let your agent build your analytics
322 followers
Dex is an open-source CLI that lets your agent build your analytics. It comes with skills out of the box. Install it in any coding agent, then point it at your data. Dex does ETM: Explores the landscape → Transforms your data into models and metrics → Maintains them by fixing drift before it reaches production.
This is the 2nd launch from Dex by Exmergo. View more
Dex Semantics
Launched this week
Dex Semantics adds declarations to your analytical models, which capture row meaning, join nature, how numbers add up, and decisional assumptions.
Thanks to this, Dex scores 80% on ADE-bench with Claude Sonnet 5.5, compared to 73.3% without Dex (25% fewer tasks failed).
Declarations live in your models as code, not a third-party tool. Dex then helps your agent convert declarations into your Semantic Layer of choice.
Free
Launch Team / Built With
TinesThe single, secure environment for agents, apps, and automations.
Promoted
The YAML semantic layer is the part that caught my eye — most agent-built dashboards I've seen fail on inconsistent metric definitions, not on SQL. Curious how you handle it when two teams define the same metric differently, or when a definition drifts from what's actually in the warehouse?
@jcbuilds
`dex maintain` is all about handling this problem! https://github.com/exmergo/dex/blob/main/skills/maintain/SKILL.md
Interesting point. We recommend, at an organizational level, to define one semantic layer per vertical (finance, ops, internal metrics etc.) so that this doesn't happen.
Our enterprise offering is all about handling these types of problems at scale, with our agentic workflows: https://trydex.ai/enterprise
Hi Marco, congrats on the launch!
I'm a terminal nerd, and Dex sounds like it's really cool. I'm going to check it out.
@nathan_tarbert Awesome! We specifically built Dex as a CLI tool to have both people and agents be able to work with it. No MCP or login needed, just install the CLI (and skills, if you want to give your agent the guidelines on how to use Dex) and let it rip!
@nathan_tarbert a fellow terminal nerd! let us know how it goes 🙌
@emna_rahmouni, terminal nerds need to stick together :)
What ide do your team use to build this beauty?
Let's goooooo!
@gtmnerd I ♥️ GTM
Fixing drift before it reaches production is the part I'd care about most, that's usually where analytics quietly breaks. Does Dex flag the change for a human first or fix it on its own? Good luck with the launch!
keeping how numbers add up right next to the model is the right place for it, a summed ratio looks totaly plausible on a dashboard and nobody notices
when a declaration goes stale after a schema change, does Dex flag it before the agent relies on it??? feels like the obsolete assumption from your quote all over again
@thamibenjelloun 100%, that's what the `dex maintain` commands are all about!
You can run the maintain commands in agentic workflows or in CI, to make sure that a schema change gets flagged. Your agent can then check the declared assumptions vs the schema drift and update the data models (and declarations) accordingly!
The declarations-as-code approach is what caught my eye — keeping row meaning, join nature, and how numbers add up inside the model itself rather than in a separate tool feels like the right call for drift. Curious about the remaining 20% on ADE-bench: which kinds of tasks still fail even with Dex, and are they mostly ambiguous business logic, or things the declarations can't capture yet? Also, does the CLI work outside dbt, e.g. with plain SQL models?