The tool seemed to me to be a good solution to extend the functionality for customers who host websites with us. This makes me a bit different with the usage scenario than developers who prefer to trigger the same flow automatically every time (and thus the solution with macros for always the same login as a usable sub-package is ideal). My idea would rather need the planned extension to context (with which, for example, the same flow can be used multiple times with different credentials). But this functionality is still in development ... and so I could not bring myself to a larger Tier.

One of the biggest advantages of dogq is the ability to invite as many team members as you want ..... With other solutions this drives you crazy when you have to think if you can invite someone else or if the shared login credentials are the easier solution after all. The structure with scenarios, macros and the resulting workflow as well as the existing scheduling function form a good basis for the further development of the tool.