Decision guide
When NOT to use EntiHub
The fastest way to success is to avoid mismatched use cases early.
Not a fit right now
- You need a fully custom workflow engine as a primary requirement.
- You are not ready to define ownership for critical master domains.
- You need a one-time data cleanup project only, without long-term governance.
- Your organization cannot run any MDM workload in its own infrastructure.
When EntiHub is a fit
- You want governed master data in your Azure tenant — Fabric, Azure SQL, PostgreSQL, Oracle, or MySQL.
- A lean data platform team can own YAML, API, and release workflows.
- You need measurable value in weeks, not a multi-quarter platform program.
- Approvals, audit, and integrations matter — without a separate MDM project army.
Often a better first step
- Start with one high-impact domain (customers, suppliers, or product reference).
- Define data owner roles before onboarding many teams.
- Automate one integration flow first, then scale to additional systems.
Quick readiness checklist
- Clear sponsor and owner for each target domain.
- At least one consuming system that benefits from consistent master data.
- A small technical team that can own YAML, API, and release workflows.