FINALES is designed to be easily installable in any computer and to be self-contained, so that a new independent installation (with its own independent database and secure access credentials for the tenants) can be used for a given optimisation task, thus preventing any risk of unwanted data leak and keeping different MAP optimisations fully independent. We call each installation a FINALES instance. Once capabilities and tenants are registered in an instance of FINALES, the tenants can communicate to the server through the web API endpoints. The Python framework FastAPI is utilised for constructing the RESTful API. In total, 17 endpoints are exposed to the tenants of which one handles the necessary user authentication protecting the other 16 endpoints. Several of the endpoints are however suited only for functionalities related to an optimiser and archiving tenant. A comprehensive explanation of all the API endpoints can be found in section SI-1.2. The most relevant endpoints for an experimental or computational tenant are pending requests/ for retrieving the currently pending requests, requests/object id/update status/ e.g. for changing the status of a request to reserved when it has been picked up by a tenant and results/ for posting results based on a specific request. We stress that the exact parameters in the requests might not be directly applicable to a given tenant implementation. For example, in this study, the electrolyte formulation used in MD simulations may necessitate rounding ratios to achieve an integer number of molecules, resulting in slight deviations from the original formulation. An important design aspect is therefore that the parameters reported in requests and results are allowed to differ, and both are stored in the server.