ESP RainMaker Neo Open Sources the Full IoT Stack

Espressif has released ESP RainMaker Neo, an open source device-to-cloud-to-phone platform that ships the entire stack: cloud backend, firmware SDK, firmware examples, phone app SDK, a reference phone app, and a dashboard. All of it is Apache 2.0. For anyone who has built an ESP32 project and then stalled at the question of where the data goes, this is the missing 80% of the work arriving as source.

• Complete stack under Apache 2.0: cloud backend, firmware SDK and examples, phone app SDK, reference app, and dashboard
• Neo runs on your own AWS account rather than Espressif-managed infrastructure
• Three deployment models: Public, Packaged into your AWS account, or Build from Source
• The original ESP RainMaker continues as Classic; there is no direct migration path between the two

What Ships in ESP RainMaker Neo?

The scope is the story. Most IoT platforms open source the firmware SDK and keep the cloud proprietary, which leaves you dependent on someone else's uptime and pricing. Neo publishes the backend too, along with the phone app SDK and a working reference app you can rebrand.

That completeness is what makes the license meaningful. Apache 2.0 across every layer means a small manufacturer can ship a connected product without a per-device cloud fee, and a hobbyist can run the same code for one device that a company runs for a hundred thousand. The ESP32-C61-MINI putting Wi-Fi 6 in a $2 module made the radio side cheap; this makes the cloud side ownable.

How Is Neo Different From RainMaker Classic?

The original ESP RainMaker is now called Classic, and Espressif manages its infrastructure. Neo inverts that: it runs on customer-hosted AWS, giving you control over region, retention, scaling, and cost.

Be clear-eyed about the tradeoff. Classic means Espressif handles operations; Neo means you do. You are taking on AWS billing, IAM configuration, and backend upgrades in exchange for control and no vendor lock-in. Espressif has also stated that Neo is a distinct implementation with different cloud architecture, so direct migration from Classic is not possible. If you have a Classic fleet in the field, Neo is a decision for your next product, not a weekend upgrade.

Which Deployment Model Should You Pick?

Espressif offers three paths, and they map cleanly onto three kinds of builder. Public uses Espressif-managed infrastructure and is the fastest way to get a prototype talking to a phone. Packaged deploys into your own AWS account with Espressif's configuration, which is the sensible default for a product going to market — you own the data and the bill without owning every deployment decision. Build from Source is for teams with specific compliance, regional, or architectural requirements that need to modify the backend itself.

Most makers should start Public and move to Packaged when a project stops being a project. That is the same progression that has made self-hosting practical across our mini PC and SBC coverage, from ESPHome-driven smart home builds upward.

Why This Matters for the ESP32 Ecosystem

Espressif's silicon has dominated hobbyist wireless for years on price and toolchain quality. The consistent gap has been what happens after the firmware works — the cloud, the app, the provisioning flow. Publishing all of it under a permissive license closes that gap without asking anyone to adopt a proprietary platform.

The fair caveat is that Neo assumes AWS. That is a reasonable assumption for most teams and a real constraint for a few, and the open source release at least means the code is there to adapt.

Sources: CNX Software — August 6, 2026; Espressif — August 2026.