Moxie's shutdown risk lived in its cloud, not the robot

What happened

By late 2024, Embodied, Inc., maker of the children's companion robot Moxie, was in enough difficulty that a former engineer began publishing replacement server software for owners whose devices depend on the company's cloud. That project, OpenMoxie, shows its first commit dated 18 November 2024 and describes itself as being for people 'looking for a solution to run your Embodied Moxie Robot should their cloud infrastructure shut down'. Embodied's own support site, archived on 17 December 2024, carried only a general status notice stating that 'due to an external issue, some customers may experience trouble using Moxie' and that 'partners are actively working to address the issue'.

What the documents show

Embodied's own marketing site, archived 30 December 2024, was still live and describing Moxie in its original terms — 'the world's most advanced AI learning robot', founded by Paolo Pirjanian to bring 'emotional intelligence to artificial intelligence' — with no shutdown notice visible on the homepage itself. That gap, between a still-normal public homepage and a support page vaguely blaming 'partners' for service trouble, is itself a documented fact: nothing opened for this record shows Embodied issuing its own plain statement that the company or its cloud service had closed. The clearest documentary evidence of an actual disruption is indirect — a former engineer's decision, within weeks, to build and publish replacement infrastructure.

The mechanism

Moxie's dependency on Embodied's cloud is what OpenMoxie's own README describes replacing: a 'local network hub' that restores 'Daily Missions, Reading, and Wild Workout' features while acknowledging that newer modules, such as Ocean Explorer and Story Maker, 'are missing' without the original servers. This is the mechanism worth naming plainly: a physical robot's core behaviour, in a cloud-dependent design, is not stored on the device but rented from a server the manufacturer controls, so a business failure at the company is also, immediately, a functional failure of hardware already purchased and sitting in a child's bedroom.

What it leaves open

This record does not establish an exact date on which Embodied ceased normal operations, why, or under what legal process, because no company statement fixing those facts was found in the documents opened for it; the dates above reflect an archive timestamp and a repository's founding, not a company announcement. This is an editorial reading, not a stated fact: the absence of a plain company statement is itself informative about what a cloud-dependent purchase leaves owners without, at the moment they most need clarity.

• Does a company that stops operating normally say so plainly, or only through a vague service notice?
• Which features live on the device itself, and which depend on a server the company can turn off?
• Who has stepped in to document or replace a disrupted cloud service, and on what evidence?

The clearest record of what happened to Moxie is not a company announcement but the code a former engineer felt compelled to publish. That fact alone says something about what cloud-dependent companion hardware asks its owners to trust.