The article omits that Wero is running on top of AWS. So still the same problem, just slightly lower in the stack.
The article omits that Wero is running on top of AWS. So still the same problem, just slightly lower in the stack.