If Flock has so many issues with this database, and all their solutions are patchwork, and those solutions remain local to the jurisdiction that is locally using Flock, then this is a bad product.

If you build a product on a bad database, you cannot load the blame for the resulting bad product on the bad database. If it was not fit for purpose, then the product designers are the problem as much as anything else.

This applies doubly for a product that relies so heavily on automation enabling speedy responses with heavy consequences.

I understand that this may smack of perfect being the enemy of good, but this domain is akin to medical devices in terms of impact.