Blog

Are you interested how we managed to combine Mutual TLS, The Update Framework, Over The Air updates and Release on Demand in one feature? And also how did that help Foundries.io to provide an easy and controlled way for our customers to provision secure updates to millions of devices over public networks? This blog post introduces a FoundriesFactory Waves feature that will be publicly available at the start of Q2 2021.

At the dawn of 2021 Foundries.io delivered a new simple yet powerful way to manage your FoundriesFactory devices. We call it "device groups" and as a name suggests it basically allows to categorize devices belonging to a single Factory into user defined groups.

As the range of IoT and Edge devices continues to increase, many companies are now having to support applications and services across multiple device types, sizes and underlying architectures.

As Edge devices become more integral to both our domestic and commercial lives, the requirement for devices to be available whenever you want them is critical. Added to this, the ability to keep devices updated so that they remain secure and equipped with the latest features provides consumer confidence in the product, as well as helping to secure repeat purchases.

The one thing this year has reminded us is how uncertain things can be and how we always need to be prepared for unseen issues. This is also applicable to our Edge devices. Having the ability to update Edge devices throughout their lifespan is now a fundamental feature of any connected device.

As the creator of aktualizr-lite, I often underestimate the difficulty in understanding what aktualizr-lite is trying to do. Rather than typing the same few things in Slack over and over, I thought I'd try to write down what aktualizr-lite is "thinking".

It has been a busy and exciting year on the technical side at Foundries.​io. We have been laser focused on extending our FoundriesFactory product feature set based on the requirements of our customers. The intent for these features is to make it easier and faster to build and maintain secure products on our platform.

Talking about security requires precision. However, precise language can be hard to digest for even most technical audiences. What follows is what I call a "pepperoni pizza" article. It's nobody's first choice, but most everyone can eat it.

Part II of the fiotest series series will focus on some examples of what you can do with fiotest. Hopefully you'll find some inspiration and things you can copy/paste into your own tests.

We've been using a tool called "fiotest" for months now, but haven't really explained the what, why, and how. This is the first part of a small series of articles to explain fiotest.