Given our safety and security protocols, readers of this manuscript may not execute HELAO-async code with our laboratory equipment. While we encourage the duplication and adaption of our hardware and/or software for operation in other labs, we have built a virtual demo for the present purposes of introducing HELAO-async. To create a minimal implementation of Fig. , the demo contains 2 independent Orchestrators, each with a dedicated Action Server that simulates the acquisition of electrochemistry data to characterize the overpotential for the the oxygen evolution reaction (OER). We have packaged previously-acquired electrochemistry data with the demo. The 2 Orchestrators share a common resource, which in practice may be the robotic sample handling system. In the demo, the shared Action Server is an active learning agent that manages requests for new acquisition instructions from the 2 Orchestrators. This shared-resource Action Server runs independently and is unaffected by the runtime of each Orchestrator, which is demonstrated in the demo by independently starting and stopping the Orchestrators, representing the asynchronous operation of research workflows within one or across multiple laboratories. Running the demo batch script will open 5 user interface browsers, 2 Operators that control the respective Orchestrators, 2 Visualizers (Observers) that show the data streams from the respective electrochemistry Action Server, and a Visualizer (Observer) for the shared active learning Action Server. This Visualizer shows the progress of the active learning campaign, including the contributions from each of the indepen-Fig. A screenshot from the HELAO-async demo. The command line windows are a. the miniconda python environment from which the demo was launched, b. the instance of the first Orchestrator "demo0" and its Visualizer, c. the instance of the second Orchestrator "demo1" and its Visualizer, and d. the instance of the Visualizer for the shared Action Server "GP SIM". e,f. The web user interfaces for the Operators for the Orchestrators. While various experiment controls may reside in these web interfaces, the demo involves automated execution of active learning campaigns as programmed in the sequence "OERSIM_activelearn." The three Visualizers are g. for the GP SIM Action Server, as well as h. and i. for the electrochemistry Action Servers orchestrated by demo0 and demo1, respectively. The GP SIM visualizer (g.) shows (top) the most recent communication with an Orchestrator, (bottom) a list of recent acquisitions, and (middle) histograms showing the distribution of catalyst overpotentials. The 4 histograms correspond to the 2 combinatorial libraries associated with their respective Orchestrator and and the 2 types of overpotentials, those previously measured and those predicted by the Gaussian Process for unmeasured compositions.