MDM Studio installs on-premises, in your private cloud, or as an isolated tenant on a managed hub. The hub lives next to the databases it masters, with no third-party SaaS egress.
A lean Node.js service and a modern React studio, delivered as versioned releases or Docker images with TLS termination included. One VPS is enough to start — or run it as an isolated tenant on a shared hub.
No SaaS middleman and no third-party egress. Each tenant’s master data, credentials and audit trails are isolated from every other tenant and encrypted at rest; every privileged action is logged.
Self-bootstrapping migrations per engine, built-in health diagnostics at login, hub housekeeping tools and a versioned, auditable upgrade path.
The latest v1.2.0 update changes two pipeline behaviours, each with a report that names exactly what will change on your hub before you run anything. Field transforms now execute — the transform-impact report lists every mapping whose output moves; nothing already landed is rewritten. And approved specification versions now govern runs — approving a mapping set freezes an immutable version the pipeline executes; sets never approved keep running their drafts, and the spec-impact report names the ones that diverge. Run both reports before the first post-upgrade pipeline run, and the first changed value is a decision, not a surprise. Full details are in the User Guide's Before you upgrade section.
From a single evaluation VPS to a multi-tenant production estate — we'll help you size and stand it up.