Dex Enterprise | Self-Building Analytics, Owned by Your Team
Self-building analytics, owned by your team
A harness for Dex, deployed on your infrastructure. Scope the question. Build the change. Catch the drift. Tested dbt changes arrive as draft pull requests, and your team decides what ships.
Features
- ✓ Deployed on your infrastructure
- ✓ Opens a draft pull request
- ✓ Never merges it
Sources to reviewed change
- PII flagged
- Reviewed diffs
Your agent
Your BI
Your CI
Scope
scope run 1841
Data work never arrives in one neat queue.
Some of it starts as a question nobody has scoped. Some sits in the backlog as a ticket. Some shows up as a broken model on Monday morning.
Questions nobody has scoped
- How should we measure net revenue?
- Can our data support a churn metric?
- What would it take to track repeat purchases?
Tickets in the backlog
- DATA-418 Add net revenue metric
- DATA-402 fct_orders duplicated after backfill
- DATA-397 Align churn definition with finance
Drift under your models
- schema: stripe_id dropped from raw.users
- grain: orders_daily lost its unique key
- semantic: net_revenue no longer matches finance
Dex Enterprise works all three queues.
Every workflow runs open-source Dex, the same Apache 2.0 engine your engineers can install today. You can read it before you buy anything.
Scope. Build. Fix.
Three workflows, one for each kind of work. Run them in order, or start with the one you need.
Scope · trigger: a goal
Describe what you want to measure. Dex explores your data and dbt project and posts a scoping report to the ticket: the data that exists, the decisions still open, the risks, and draft requests for the work.
Build · trigger: a ticket
Send Dex a ticket, or a draft request from Scope. It reads the project as it is right now, writes the change, builds it on your dev target, and opens a draft pull request linked to the ticket.
Fix · trigger: a schedule
On a schedule, Dex checks your data against the baseline your team accepted, across schema, volume, grain, and semantics. Mechanical fixes arrive as draft pull requests. Anything that needs judgment becomes a ticket that names the decision.
What Dex can change
Writes
Proposed in a draft pull request.
- Model SQL
- Tests and docs
- Semantic definitions
Flags for a person
- Definition decisions
- Project config
- Package dependencies
Never touches
- Branch and merge rules
- CI workflows
- Access and secrets
Deployed on your infrastructure. Your data stays with you.
The harness is deployed on infrastructure your team already governs and runs in your own CI, under identities and keys you own. Exmergo never receives your data.
Frequently asked questions
What is Dex Enterprise?
Dex Enterprise is a harness that runs open-source Dex for a whole data team, deployed on your infrastructure. It has three workflows: Scope, Build, and Fix.
How is Dex Enterprise different from open-source Dex?
Open-source Dex gives one analytics engineer the Explore, Transform, Maintain loop on demand, while Dex Enterprise is the harness that runs the same engine for the team.
Can Dex Enterprise merge changes on its own?
No. It opens draft pull requests and stops there. Your reviewers decide what becomes part of the project.
Where does Dex Enterprise run, and does Exmergo see our data?
The harness runs in your CI, as an app you register, with your own data credentials. Exmergo never receives your data.