Supported hardware

Overview

MDK integrates field hardware through Workers. Each Worker declares what it supports in its mdk-contract.json. For an MDK-maintained Worker, that contract is the single source of truth for coverage. For a manufacturer-maintained Worker, external-workers.json decides whether it appears in the catalogue at all, and its contract may not enumerate every supported model or firmware version. Where it doesn't, the manufacturer's own documentation is authoritative, not this page.

Supported Workers

A Worker contract may be defined by the supplier, such as a hardware manufacturer. Alternatively, MDK may create and support Worker contracts.

Manufacturer-maintained Workers

Some manufacturers build and publish their own MDK Worker, maintained in their own repository rather than this one. MDK fetches and schema-validates each manufacturer's mdk-contract.json at generation time, so the catalogue reflects the current contract without copying it into this repo. The manufacturer's own repository, not MDK, is the authority on what device and firmware combinations it actually supports. See the generated catalogue for the current list and each entry's repository link, and the run guide for how a manufacturer-maintained Worker is hosted.

MDK-maintained Workers

Everything else ships in this repo, with a bundled mock and unit and integration tests.

Full catalogue

For brand, model list (where the contract enumerates one), and Worker type, see the generated catalogue, generated from every in-repo mdk-contract.json plus the manufacturer-maintained list. Where a manufacturer's contract doesn't enumerate models, the catalogue says so explicitly rather than implying none are supported. Check that manufacturer's own documentation instead.

Next steps

• Terminology: Kernel, Worker, manager, thing, mock
• Deployment topologies: decide how to run the Worker service
• Run a miner Worker: host a manufacturer-maintained or MDK-maintained Worker