Apologies for the slow response (there has been some staff unavailability slowing processes).

In T416590#12120473, @BLiviero-WMF wrote:

Can you say more about database quotas, what do you anticipate the growth to be over time, to what maximum limit?

This is extremely useful, thanks @bd808. We will migrate to a fully compliant RDBMS and both MariaDB and PostgreSQL seem like good candidates. We are prioritising faster access and scalability. The Database as a Service offering you mentioned looks like a great solution. It has the added benefit of removing the computational DB load from the project server. Our tool cannot run in Toolforge, so we would be looking at Trove, which poses some questions:

Many thanks for picking this up Bryan. As part of the separation of the functionality outlined above, we are revisiting the database provision on both sides.

Dear Francesco,

Thank you very much! I have just opened a new task with details and diagrams and will communicate via other tasks leaving this closed.

Hi @Andrew and @fnegri.

Thank you @Andrew and @fnegri.

I think we managed to create and link the developer accounts to the accounts 1. and 2. above. I hope we followed the right procedure. Please let me know if this is now OK. I really appreciate your support.

If we can have three admins, these would be them in this order of priority please:

Thank you Francesco (and Andrew). We will satisfy the requirements and ensure everything is transparent to allay any community concerns.

Hi Andrew,

The work that @maiarocg suggested above has been implemented and is available for trial with details at Introduction to ProVe. There is also an API and the tool is going through continuous development.