Within tomato, the user supplies a definition of devices, which represent and track the state of the controlled instruments. Such devices can be arbitrarily combined and addressed into pipelines. For instance, in a multi-channel potentiostat, each channel of the device can be addressed independently using the appropriate pipeline. The experimental protocols (YAML or JSON files) can be either written and submitted manually, or deployed by AiiDA. The protocols are interpreted into a language understood by the hardware by tomato's drivers. This implies the development of ontologies, or vendor-agnostic domain specific languages; see e.g. Refs. 33 and 34 for current efforts in heterogeneous catalysis and in the battery communities, respectively. The parsing of the raw instrumental data into a FAIR data format, understood and stored in AiiDA, is performed automatically and periodically by the FAIR data parser yadg. Currently, tomato supports a wide range of BioLogic potentiostats, using a Pythonbased shim around a vendor-supplied DLL. An extension of the driver library is currently underway.