* more explicit on products are open source * explain overlap between all products and services: buckram * how are client services open source exactly? Surgery, offshore structures, bridges and spacecraft. When we simulate life-critical engineering, we need to understand the accuracy of our tools in each specific scenario. To do this, we need to know the underlying theory. A number of years ago, an entire oil rig collapsed in Norway, as a result of this lack of understanding. When I was working in engineering, we needed to check which established theory was used by a common proprietary tool we used for all those applications. They told us that was commercially sensitive information. If there were accepted open tools, transparent and without vendor lock-in, could we justify buying from that closed provider again? At that point I realised that closed source, as an economic model in critical industry applications, has a finite life. Now think of all the contexts where transparency and accountability are critical in software - hospitals, government, courts, data security, cybersecurity. That may seem positive for free software's future, but only if it is self-sustaining without the closed source ecosystem - core developers not having to rely on proprietary or research-only employers to keep them fed. I believe open source is normally more economically efficient and socially beneficial than closed source, so FLOSS should be a safe business bet in the long-term. I quit my job several years ago to test this, and discovered you need to eat in the short-term. First a couple notes