During development, we tested whether a tiny microcontroller could act as a thin client to a cloud AI model — connecting to your WiFi, sending a prompt to a provider's API, and displaying the reply on Nameless's OLED face. It worked. We took it out anyway.
The prototype, briefly
- The ESP32-C3 would connect to a WiFi network.
- You'd pick a cloud AI provider and paste an API key during setup.
- The device would send your message to that provider's API over the internet.
- The response would render on the 128×64 OLED face.
It was a neat piece of engineering. But it meant the device depended on your WiFi, sent data off the desk to a third party, and needed an account and an API key just to work.
Why we took it out
A desk companion sits next to you all day. We decided that trade-off wasn't worth it for a device that's meant to feel private and low-maintenance:
- Zero data collection. Nameless has no camera, no microphone, and no network connection to send anything over even if it wanted to.
- No account, no key, no setup friction. Nothing to configure, nothing to pay for, nothing to expire.
- Works anywhere. No dependence on your WiFi network being up, in range, or even present.
- Nothing to leak. An offline device has no cloud connection to be compromised.
What Nameless does instead
All of Nameless's features — the virtual pet engine, mini-games, Pomodoro timer, and breathing coach — run entirely on-device, offline, with nothing ever leaving the desk. For a companion robot, we think that's the right trade: less clever, more trustworthy.