Brittleness in verification describes the phenomenon where seemingly inconsequential changes to a program being verified, or to the verification tools, cause the outcome of verification to change. Using multiple SMT solvers mitigates proof brittleness and improves verification performance. When implemented in the cloud it provides multi-developer team consistency. While it can introduce new challenges such as soundness concerns, energy use, and network congestion, those can be mitigated. We believe it is the right default for many Dafny use cases, especially on large codebases with more than one developer.