We manage 20+ Firefox extensions today, and that number will soon grow to 40+. During coordinated releases, we regularly hit AMO signing throttles.
Our setup is one extension per customer, to ensure strict isolation between customers. We are also fully self-hosted. The main operational problem is that nearly every release runs into throttling, which makes deployment difficult and unreliable.
I would like to understand whether Mozilla provides any approved approach for publishers in this kind of setup. Is there any recommended higher-volume signing workflow? I not, are there any account-level adjustments or exceptions available? Is there a best-practice release strategy for teams managing many separate extensions?
At the moment, the throttling during signing is our main bottleneck, and we would appreciate any help dealing with this.