The development of Newton-X NS has been driven with efficiency in mind. More precisely, when talking about efficiency, we had three different topics in mind: 1) pure computational performance (optimize, in particular, the input/output operations), 2) data management standards that allow for easier sharing and more streamlined data production, and 3) keep the entry barrier for new developers as low as possible. The first point leads us to switch from a collection of Perl scripts to a monolithic Fortran code, allowing direct data exchange between the different parts of the code through memory, not text files. This redesign effectively reduces the time spent in read/write operations, which is particularly useful when using built-in analytical models. In those cases, no external electronic structure code is invoked, and the dynamics can be up to 2,000 times faster than with Newton-X CS. Having a monolithic code also helps with point 2). We chose the H5MD file format, 116 based on the Hierarchical Data Format 5 (HDF5) framework. Our monolithic implementation allows us to open the interface only once, and we can write the outcome of the dynamics to disk at one specific point in the code. In that way, we can be sure that the data written is always consistent. This data format is widely supported and implemented in several quantum-chemistry software (such as LAMMPS, 117 Molcas, 118 and MLatom ), so we can benefit from the tools already developed for tasks like visualization of the dynamics (VMD 119 plugin). The HDF5 library also binds to popular scripting languages such as Python or Julia.