A custom-branded maintenance platform can carry the client’s chosen name, logo, colours, terminology, forms, reports, and approved domain. That presentation does not automatically transfer ownership of the underlying software.
Client operational ownership
The client should own its asset information, maintenance records, documents, work history, user-generated content, and operational reports. Practical export and backup arrangements should be part of the agreement.
Authorised client administrators should control users, roles, assets, workflow settings, and daily operation within the agreed service scope.
Provider platform ownership
The technology provider may retain the reusable platform core, source code, common components, security improvements, and shared product development. This enables one maintainable product instead of multiple uncontrolled forks.
What the agreement should define
The implementation agreement should distinguish:
- branding and approved attribution;
- operational control;
- data ownership, export, backup, and retention;
- hosting and deployment model;
- support, updates, and service levels;
- configured features and planned features;
- integration scope;
- termination and transition arrangements;
- any source-code transfer or buyout.
Full white-label presentation can be a commercial option. It should never be described as source-code ownership unless the contract actually transfers that ownership.
Scope note: This general information does not replace a site-specific engineering assessment, manufacturer instruction, statutory requirement, or competent specialist advice.