Hardware

Today marks the first implementation of running the entire Golioth firmware stack on a modem processor. This dramatically reduces resource consumption on the external MCU processor, and makes it easier to add Golioth to any hardware or platform.

We regularly refer Golioth users to our trusted Design Partners to help design, test, and deploy hardware out into the world. The Golioth Design Partner program has been going for more than 2 years and continues growing. In 2025, we reached 20 listed partners, with others in the wings.

The Thingy:91 X is an upgrade to the original Thingy:91 which enables new features like WiFi, additional sensors, upgraded memory partitions, and new connectors to make extensibility a breeze. Best of all, it already works on Golioth!

Your ESP32-C3 can act as a secondary modem for any type of primary processor. This post shows how to program and utilize the ESP-AT default firmware.

Bluesky has seen a large increase in its number of users over the last few weeks. To learn more about how the AT Protocol works, we set up a Pipeline to allow for microcontrollers to post to Bluesky via Golioth.

As we previously wrote about, we attended the first Embedded World North America, held in Austin Texas...

If you have ever tried communicating with a device on a private network, you may have encountered Network Address Translation (NAT). Because the number of connected devices has long outpaced the number of unique addresses in the IPv4 address space, public IP addresses have to be shared between devices. This introduces a number of challenges.

Did you know that Zephyr doesn't have a plain old GPIO example? The closest thing is the blinky example that controls LEDs. Why is that? Zephyr expects you to write your own devicetree bindings. It's not that hard, and it's the topic of today's post.