Define
Describe the entity and validation rules in YAML — or let AI draft it from plain language.
Governed knowledge layer · in your Azure warehouse
Define entities in YAML. Govern with approvals and history. Let people, apps, and AI agents use the same source of truth — in Fabric, Azure SQL, PostgreSQL, Oracle, or MySQL. Your data stays in your subscription.
Want the deep dive? Full product tour on Features →
Not only classic masters — a governed layer for knowledge that AI and business decisions need. Why this positioning →
Corporate vocabulary AI agent registry Business rules Decision rights KPI definitions Exceptions Supplier critical-change Cost centers & FX sets Classic master data
What changes when knowledge, rules, and data share one governed surface.
| Before | After |
|---|---|
| Business rules in SQL, Power BI, Excel, and people's heads | One approved rule catalog — API for apps, BI, and agents |
| AI invents what “customer” means | Approved corporate vocabulary with synonyms and exclusions |
| “Can I offer 35% discount?” — nobody knows the policy | Decision rights registry with limits, owners, and approvals |
| Same customer in 5 systems, different data | One authoritative record — and classic MDM when you need it |
| Anyone changes anything without oversight | Approval workflow for sensitive changes, with full history |
| IT deploys MDM for months | Setup in minutes, new entity in minutes — in your Azure |
From definition to a source of truth people, pipelines, and AI agents can trust.
Describe the entity and validation rules in YAML — or let AI draft it from plain language.
One click creates the table in your warehouse. Preview schema changes before redeploy.
Enter and manage data via web UI, bulk import, or REST API.
Approvals, role-based access, and a complete audit trail of every change.
Power BI, ERP, CRM — and AI agents — read the same validated data and rules.
The outcomes that matter — details live on Features.
Rules, definitions, decisions, and master data in one warehouse-backed model — not five spreadsheets and a wiki.
Agents look up approved vocabulary, decision rights, and evidence instead of inventing policy in the prompt.
Bad data never enters. Approvals for sensitive changes, Entra ID RBAC, history, and Enterprise audit when you need it.
Install from Marketplace, billed on your Azure invoice. Data stays in your infrastructure — start in minutes, cancel anytime.
Pick the path that matches your priority.
Give agents a governed contract — vocabulary, rules, and entitlements — via API and the entihub CLI.
Unify dimensions and KPI definitions for Power BI and Fabric without reconciling exports across teams.
Own cost centers, FX sets, allocation keys, and reporting definitions as approved entities — not Excel versions.
Approvals, decision evidence, and role-based controls — without moving data out of your Azure environment.
Also common: Customers & suppliers Products & pricing Cross-system ID maps Compliance obligations Power BI dimensions
Scale by features — not by user or entity counts. Billed through Azure.
Agents look up approved terms, decision limits, and evidence — they don’t invent policy.
The same lifecycle works from the UI, CI/CD, and the entihub CLI.
YAML drafting from plain language is available when you stand up a new entity.
entihub entities list --json
entihub entities data list Term --filter "[name]=Customer" --json
entihub packages deploy --file knowledge-package.zip --json
Ready when you are
Install from Marketplace and try it yourself — or book a 30-minute fit call. Cancel anytime. Nothing locks you in.