Lynx Product Directions: The Three Horizons

We have defined three fundamental horizons that have become a framework of everything that we are doing at Lynx. The first horizon is what I will call platform play, which is fundamentally how we can deliver more software value to the customers so that they can do less on the platform and more on the application. Think about not only operating system and hypervisor, but more broadly to include aspects of middleware and Linux. Linux is certainly a critical piece of our thinking and is another asset that you can run on the infrastructure. We also include toolings that enable the customer to develop their application more efficiently.  

Horizon two is where we start to embrace cloud native and DevOps or DevSecOps methodologies. What you can expect from a roadmap and offering point of view is for Lynx to enable customers not just to use DevOps and DevSecOps, but to augment their pipeline with what they need to develop and deploy devices that incorporate technology like LYNX MOSA.ic into their platform. 

Overall, horizon 2 is fundamentally a productivity play. This is really about assisting the customer to accomplish things faster, better, and in a more predictive way to increase the overall quality of their device.  

Horizon three enables the customer to orchestrate and service their device once they are field deployed. Think about things such as a feedback loop which is fundamentally how you are enabling observability of the deployed device and enabling the device to send back information about the health of the device or cybersecurity risk or anything else. Most services can be deployed into those devices.  

These three horizons are not being worked on sequentially. While most of our efforts, at least in the public domain, have been in association with LYNX MOSA.ic as a platform, we have already accomplished a little bit of two and are touching on horizon three. 

The path to get there will include internal development, partnerships, and acquisition. The Military and Aerospace markets are clearly struggling in this world of mounting system complexity to deliver projects on time and inside cost estimates. The “IC” in LYNX MOSA.ic stands for integration center. This means that if there is acceptable technology in the marketplace, we will be looking to prove out the operation of that technology within the LYNX MOSA.ic software framework as opposed to creating our own technology. We will also look to take on the task of proving out the operation of compelling, complementary technology with LYNX MOSA.ic. This means ensuring Guest operating systems (and therefore customers’ legacy software) and be executed unmodified inside LYNX MOSA.ic. You will hear more about that in due course.