Abstract: Boot firmware for a computing device can be modularly and dynamically composed to facilitate implementing changes and updates to a computing device's firmware. The firmware image can include a primary module, which is responsible for certain basic initializations, and a module list, which can include a listing of additional modules that are to be executed during the boot procedure. The module list can be used to identify and access the selected modules from a module library, such as via globally unique identifiers (GUIDs). Once acquired, the selected modules can be executed, taking into account required dependency modules (whether included in the selected modules or not) and configuration settings. The module library can be stored entirely locally (e.g., as part of a distributed firmware image), entirely remotely (e.g., accessible via network connection), or a mixture of locally and remotely.