Blog

Secure OTA updates and a unified software platform are the keys.

A fairly common question I get asked is how Factory devices securely pull container images from our Docker Registry, hub.foundries.io. It's kind of interesting, so I thought I'd explain.

A Foundries Factory is a unique new concept. Conceptualizing a Factory can sometimes seem difficult. I've encountered this enough to see a common problem - we are looking at things the wrong way.

Back in December, we laid out a roadmap for container orchestration. Then the dust settled from the Docker spinoff. What we now know is that Docker Apps is an inactive project. tldr; It's not a big deal for our customers and they are going to automagically get something better very soon:

Over the last month our engineering team has been working on a way to provide our customers an easy-to-use mechanism for managing on-device configuration. The result is a new project we call "fioconfig".

Built on a vision that the latest software is the most secure, software updates are central to the FoundriesFactory security story. What happens, however, when software delivery is compromised? Is recovery complicated? Enter TUF key rotation!

We strongly believe in the power of containers for embedded development at Foundries.io. However, in a world of buzzword bingo like Kubernetes, serverless, and Edge, people working on 32 bit Arm hardware would be right to feel neglected. This article discusses one way we are helping: building armhf containers efficiently.

In less than a decade, containers and, subsequently, container orchestration have exploded into almost every modern development stack. We explore just how easy it is to get Kubernetes up and running within the LMP.

Container orchestration in the embedded space lacks a good story and vision. This article explains where we currently are and what we have planned for the future.