Skip to content

OEM and Headless Integration

HeimerClean's OEM integration pilot lets a Windows x64 application use the maintenance engine through its own interface. The partner controls its screens, customer consent and application workflow.

Integration layout

Your C++ UI
    -> HeimerCleanOem.dll (C ABI)
        -> authenticated API on 127.0.0.1
            -> HeimerCleanOemRuntime.exe
                -> shared HeimerClean engines

Job events -> optional signed HTTPS webhook -> your server

The DLL is the native integration interface. It ships with a separate headless runtime folder containing the Python/AI dependencies; it is not a single DLL containing the entire engine. The runtime does not launch the HeimerClean desktop UI, tray or browser sign-in flow. The normal desktop application is not a runtime dependency.

Component Version / role
Shared engine baseline 2.2.9
Local API 1.0, integration pilot
Native SDK 0.1.0, Windows x64, C ABI
Host application Your C++ executable and UI

Available in the pilot

  • Read runtime capabilities and sanitized license status.
  • Activate an OEM-enabled company license for the agreed partner and protocol.
  • Automatically activate from a partner's prepaid stock pool without a customer account. See OEM stock licensing.
  • Run a read-only temporary-file scan.
  • Start an explicitly consented cleanup/memory optimization job using the shared engine guards.
  • Poll progress, results and events; safely cancel queued work.
  • Read local AI model progress without starting autonomous scheduling.
  • Receive optional authenticated job notifications at your HTTPS endpoint.

Continuous autonomous AI scheduling, privileged Windows repair, Defender/startup changes and installer/update control are not pilot API operations. Their lifecycle and permission requirements are tracked separately. Do not treat a normal desktop license as an OEM entitlement.

Start integrating

  1. Agree a partner ID, protocol reference, license supply and process/update ownership with HeimerClean.
  2. Obtain the reviewed x64 pilot SDK and complete runtime folder from HeimerClean.
  3. Follow the C++ quickstart.
  4. Use the local API reference for your UI's actions and results.
  5. Add webhooks if your server needs remote job notifications.
  6. Review shared-engine compatibility and acceptance gates before customer deployment.

The published guides describe the implemented pilot contract. They are not a declaration that a publicly signed production OEM installer or partner-certified application is available.