Glossary Updates12 new terms added to the glossaries · October 2, 2026, 22:44 CEST
AI TechDocKnowledge
  • English (US)
  • English (UK)
  • Deutsch
All context cards

Context card

Four types of SDK compared

What distinguishes developer, publishing, platform and hardware SDKs?

By knowledge.aitechdoc.world

Reviewed

Review log and changes

The short answer

All four are software development kits — bundles of libraries, tools, documentation and samples — but they target different things. A developer SDK wraps a remote service or API, a publishing SDK transforms structured content into output formats, a platform SDK extends a host application from the inside, and a hardware SDK exposes a device or processor to software. The target decides the artifacts, the users and who calls whom.

For: Technical writers, developers and project managers who work with SDK documentation

Key points

  • Developer SDK: client libraries for an API or cloud service; the application calls the service.
  • Publishing SDK: transformation pipelines for structured content such as DITA or XML; content flows through stages to outputs.
  • Platform SDK: extension points, manifests and sandboxed APIs of a host application; the host calls the extension.
  • Hardware SDK: drivers, abstraction layers, toolchains and debuggers for a device or processor; software meets physical constraints.
  • The name "SDK" alone does not say which of the four is meant — the target does.

The context

One term, four targets

A software development kit bundles what is needed to build on a given base: software libraries, tools, documentation and samples. What differs is the base.

  • A developer SDK wraps an application programming interface, usually of a remote service.
  • A publishing SDK processes structured content, for example DITA topics and maps, into HTML, PDF or other outputs.
  • A platform SDK gives access to the extension model of a host application such as an IDE, a CRM or an e-commerce system.
  • A hardware SDK provides device drivers, firmware interfaces, a compiler toolchain and debugging tools for a specific device.

Direction of control

In a developer SDK the application calls the service. In a platform SDK the host calls the extension at defined points. In a publishing SDK content passes through a pipeline. In a hardware SDK software calls down into layers that end at registers and signals.

Further reading

The subject area Software development kits compares the four types in a table; each has its own encyclopedia article.

Questions readers ask next

Is every SDK a set of libraries for an API?
No. That describes developer SDKs. Publishing, platform and hardware SDKs also contain transformation engines, extension frameworks, toolchains or debuggers.
Can one product ship several types of SDK?
Yes. A device maker may ship a hardware SDK for the firmware and a developer SDK for its cloud service; they are still separate kits with separate targets.

Sources

  1. Windows SDK — Microsoft Learn
  2. DITA Open Toolkit — DITA-OT project
  3. Extension API — Visual Studio Code
  4. CUDA Toolkit — NVIDIA

Review log and changes

Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.

Reviewed

No corrections or additions since publication.