The MeltX Governance Suite is the control plane of the platform, built in Pune: identity verification, property, patching, network, remote access and fleet. Each one plugs into the same asset spine that FAM, ITAM and ITSM share, so governance reports against records the platform already holds rather than against a separate inventory.
The six group into three concerns. Most organisations adopt one group first, driven by whichever is under the most scrutiny.
Who you are dealing with, verified against the source and recorded with consent. KYC Verification sits at the front of onboarding for customers, vendors, drivers and staff.
Premises and vehicles governed with the same discipline as assets: documents tracked, obligations dated, cost attributed and accountability named.
Keeping the estate patched, monitored and reachable, with the access trail an information security review expects to find.
A patch report across an incomplete device list, or a fleet report over vehicles missing from the asset register, is a report you cannot act on. The core platform is what makes the Governance Suite trustworthy.
See the whole platformDeployments that include a governance module. Engagement detail and outcome metrics are published only once the client has approved them.
MeltX FAM was deployed with a department and office hierarchy matching the zilla parishad structure. Assets were tagged and assigned to named custodians, and physical verification was carried out by MeltX teams with evidence captured in the field.
Each sector page sets out what oversight has to answer for in that setting.
The three questions that decide whether the suite is bought on its own or on top of the spine.
The Governance Suite is six oversight and control modules that run on the MeltX platform: KYC verification, property management, patch management, network management, remote management and fleet management. Each reads from the same asset records the core platform maintains.
Modules can be deployed individually, but they are designed to read from the shared asset spine. Patch and remote management, for example, are far more useful when the device list comes from a maintained IT asset register rather than from a separate inventory.
It depends on the pressure. Regulated financial organisations usually start with KYC verification. Organisations with distributed IT estates start with patch and remote management. Public bodies and enterprises with branch networks start with property or fleet management.
Configured around your asset classes before the call. Thirty minutes.