Personal blog of Yzmir Ramirez

There may be billions of IoT devices in use today, but the tooling around building (and updating) the software for them still leaves a lot to be desired. Esper, which today announced that it has raised a $30 million Series B round, builds the tools to enable developers and engineers to deploy and manage fleets of Android-based edge devices. The round was led by Scale Venture Partners, with participation from Madrona Venture Group, Root Ventures, Ubiquity Ventures and Haystack.

The company argues that there are thousands of device manufacturers who are building these kinds of devices on Android alone, but that scaling and managing these deployments comes with a lot of challenges. The core idea here is that Esper brings to device development the DevOps experience that software developers now expect. The company argues that its tools allow companies to forgo building their own internal DevOps teams and instead use its tooling to scale their Android-based IoT fleets for use cases that range from digital signage and kiosks to custom solutions in healthcare, retail, logistics and more.

“The pandemic has transformed industries like connected fitness, digital health, hospitality, and food delivery, further accelerating the adoption of intelligent edge devices. But with each new use case, better software automation is required,” said Yadhu Gopalan, CEO and co-founder at Esper. “Esper’s mature cloud infrastructure incorporates the functionality cloud developers have come to expect, re-imagined for devices.”

Image Credits: Esper

Mobile device management (MDM) isn’t exactly a new thing, but the Esper team argues that these tools weren’t created for this kind of use case. “MDMs are the solution now in the market. They are made for devices being brought into an environment,” Gopalan said. “The DNA of these solutions is rooted in protecting the enterprise and to deploy applications to them in the network. Our customers are sending devices out into the wild. It’s an entirely different use case and model.”

To address these challenges, Esper offers a range of tools and services that includes a full development stack for developers, cloud-based services for device management and hardware emulators to get started with building custom devices.

“Esper helped us launch our Fusion-connected fitness offering on three different types of hardware in less than six months,” said Chris Merli, founder at Inspire Fitness. “Their full stack connected fitness Android platform helped us test our application on different hardware platforms, configure all our devices over the cloud, and manage our fleet exactly to our specifications. They gave us speed, Android expertise, and trust that our application would provide a delightful experience for our customers.”

The company also offers solutions for running Android on older x86 Windows devices to extend the life of this hardware, too.

“We spent about a year and a half on building out the infrastructure,” said Gopalan. “Definitely. That’s the hard part and that’s really creating a reliable, robust mechanism where customers can trust that the bits will flow to the devices. And you can also roll back if you need to.”

Esper is working with hardware partners to launch devices that come with built-in Esper-support from the get-go.

Esper says it saw 70x revenue growth in the last year, an 8x growth in paying customers and a 15x growth in devices running Esper. Since we don’t know the baseline, those numbers are meaningless, but the investors clearly believe that Esper is on to something. Current customers include the likes of CloudKitchens, Spire Health, Intelity, Ordermark, Inspire Fitness, RomTech and Uber.

AWS today announced a number of IoT-related updates that, for the most part, aim to make getting started with its IoT services easier, especially for companies that are trying to deploy a large fleet of devices. The marquee announcement, however, is about the Alexa Voice Service, which makes Amazon’s Alex voice assistant available to hardware manufacturers who want to build it into their devices. These manufacturers can now create “Alexa built-in” devices with very low-powered chips and 1MB of RAM.

Until now, you needed at least 100MB of RAM and an ARM Cortex A-class processor. Now, the requirement for Alexa Voice Service integration for AWS IoT Core has come down 1MB and a cheaper Cortex-M processor. With that, chances are you’ll see even more lightbulbs, light switches and other simple, single-purpose devices with Alexa functionality. You obviously can’t run a complex voice-recognition model and decision engine on a device like this, so all of the media retrieval, audio decoding, etc. is done in the cloud. All it needs to be able to do is detect the wake word to start the Alexa functionality, which is a comparably simple model.

“We now offload the vast majority of all of this to the cloud,” AWS IoT VP Dirk Didascalou told me. “So the device can be ultra dumb. The only thing that the device still needs to do is wake word detection. That still needs to be covered on the device.” Didascalou noted that with new, lower-powered processors from NXP and Qualcomm, OEMs can reduce their engineering bill of materials by up to 50 percent, which will only make this capability more attractive to many companies.

Didascalou believes we’ll see manufacturers in all kinds of areas use this new functionality, but most of it will likely be in the consumer space. “It just opens up the what we call the real ambient intelligence and ambient computing space,” he said. “Because now you don’t need to identify where’s my hub — you just speak to your environment and your environment can interact with you. I think that’s a massive step towards this ambient intelligence via Alexa.”

No cloud computing announcement these days would be complete without talking about containers. Today’s container announcement for AWS’ IoT services is that IoT Greengrass, the company’s main platform for extending AWS to edge devices, now offers support for Docker containers. The reason for this is pretty straightforward. The early idea of Greengrass was to have developers write Lambda functions for it. But as Didascalou told me, a lot of companies also wanted to bring legacy and third-party applications to Greengrass devices, as well as those written in languages that are not currently supported by Greengrass. Didascalou noted that this also means you can bring any container from the Docker Hub or any other Docker container registry to Greengrass now, too.

“The idea of Greengrass was, you build an application once. And whether you deploy it to the cloud or at the edge or hybrid, it doesn’t matter, because it’s the same programming model,” he explained. “But very many older applications use containers. And then, of course, you saying, okay, as a company, I don’t necessarily want to rewrite something that works.”

Another notable new feature is Stream Manager for Greengrass. Until now, developers had to cobble together their own solutions for managing data streams from edge devices, using Lambda functions. Now, with this new feature, they don’t have to reinvent the wheel every time they want to build a new solution for connection management and data retention policies, etc., but can instead rely on this new functionality to do that for them. It’s pre-integrated with AWS Kinesis and IoT Analytics, too.

Also new for AWS IoT Greengrass are fleet provisioning, which makes it easier for businesses to quickly set up lots of new devices automatically, as well as secure tunneling for AWS IoT Device Management, which makes it easier for developers to remote access into a device and troubleshoot them. In addition, AWS IoT Core now features configurable endpoints.

At its annual Ignite event in Orlando, Fla., Microsoft today announced that  Azure FarmBeats, a project that until now was mostly a research effort, will be available as a public preview and in the Azure Marketplace, starting today. FarmBeats is Microsoft’s project that combines IoT sensors, data analysis and machine learning.

“The goal of FarmBeats is to augment farmers’ knowledge and intuition about their own farm with data and data-driven insights,” Microsoft explained in today’s announcement. The idea behind FarmBeats is to take in data from a wide variety of sources, including sensors, satellites, drones and weather stations, and then turn that into actionable intelligence for farmers, using AI and machine learning. 

In addition, FarmBeats also wants to be somewhat of a platform for developers who can then build their own applications on top of this data that the platform aggregates and evaluates.

As Microsoft noted during the development process, having satellite imagery is one thing, but that can’t capture all of the data on a farm. For that, you need in-field sensors and other data — yet all of this heterogeneous data then has to be merged and analyzed somehow. Farms also often don’t have great internet connectivity. Because of this, the FarmBeats team was among the first to leverage Microsoft’s efforts in using TV white space for connectivity and, of course, Azure IoT Edge for collecting all of the data.

Twilio is hosting its Signal developer conference in San Francisco this week. Yesterday was all about bots and taking payments over the phone; today is all about IoT. The company is launching two new (but related) products today that will make it easier for IoT developers to connect their devices. The first is the Global Super SIM that offers global connectivity management through the networks of Twilio’s partners. The second is Twilio Narrowband, which, in cooperation with T-Mobile, offers a full software and hardware kit for building low-bandwidth IoT solutions and the narrowband network to connect them.

Twilio also announced that it is expanding its wireless network partnerships with the addition of Singtel, Telefonica and Three Group. Unsurprisingly, those are also the partners that make the company’s Super SIM project possible.

The Super SIM, which is currently in private preview and will launch in public beta in the spring of 2019, provides developers with a global network that lets them deploy and manage their IoT devices anywhere (assuming there is a cell connection or other internet connectivity, of course). The Super SIM gives developers the ability to choose the network they want to use or to let Twilio pick the defaults based on the local networks.

Twilio Narrowband is a slightly different solution. Its focus right now is on the U.S., where T-Mobile rolled out its Narrowband IoT network earlier this year. As the name implies, this is about connecting low-bandwidth devices that only need to send out small data packets like timestamps, GPS coordinates or status updates. Twilio Narrowband sits on top of this, using Twilio’s Programmable Wireless and SIM card. It then adds an IoT developer kit with an Arduino-based development board and the standard Grove sensors on top of that, as well as a T-Mobile-certified hardware module for connecting to the narrowband network. To program that all, Twilio is launching an SDK for handling network registrations and optimizing the communication between the devices and the cloud.

The narrowband service will launch as a beta in early 2019 and offer three pricing plans: a developer plan for $2/month, an annual production plan for $10/year or $5/year at scale, and a five-year plan for $8/year or $4/year at scale.

Arm, the semiconductor firm you probably still remember as ARM, today announced that it has acquired Treasure Data, a data management platform for large enterprise customers. The companies didn’t announce the financial details of the transaction, but earlier reporting by Bloomberg pegged the price at $600 million.

This move strengthens Arm’s IoT nascent play, given that Treasure Data’s specialty is dealing with the large streams of data that these systems produce (as well as data from CRM, e-commerce systems and other third-party services).

This move follows Arm’s recent acquisition of Stream and indeed, the company calls the acquisition of Treasure Data “the final piece” of its “IoT enablement puzzle.” The result of this completed puzzle is the Arm Pelion IoT Platform, which combines Stream, Treasure Data and the existing Arm Mbed Cloud into a single solution for connecting and managing IoT devices and the data they produce.

Arm says Treasure Data will continue to operate as before and continue to serve new clients as well as its existing users. “It will remain an important part of industry IoT enablement, providing the ability to harness new, complex edge and device data within a comprehensive customer profile to personalize their products and improve their experiences,” the company says.