TEDDYCLOUD IS AN ALTERNATIVE SERVER FOR YOUR TONIEBOX

Run your child's story box on your own server so it keeps working when the company's cloud doesn't.

by toniebox-reverse-engineering community

FULL CAD BOM FIRMWARE DOCS

HomeAutomation

difficulty
●●●○○
time
an evening
license
GPL-2.0
repo
repo ACTIVE988 stars

WHAT YOU’LL NEED

  • Dev board / microcontrollerruns the project firmware

Partner

Run your scrapers in the cloudThis build needs data collection that runs 24/7. Apify's free plan includes $5 in credits every month — no card needed.Try Apify free
1

COMPAREE VERDICT

TeddyCloud replaces the manufacturer's cloud service for the Toniebox children's audio player with a server you run at home. The promise is real: nothing about what your child listens to leaves the house, and the box keeps working if the company ever switches the service off. Once it points at your own server you can also put custom audio on the figures — recordings of a grandparent reading, your own stories, anything. The catch is that you have to open the box to reach the wifi chip and reflash it to accept a new certificate, which voids the warranty and is not reversible without another reflash. The documentation is thorough and the community is active, but this is a one-time modification done carefully with the guide open, not a quick weekend hack. The server itself installs cleanly via Docker and the web interface is straightforward. Most likely to go wrong: rushing the chip access and damaging the solder pads, or skipping the certificate step and wondering why the box won't connect. If you already own a Toniebox and the idea of a manufacturer-controlled toy bothers you, this is the honest way out.

NOT IN THE REPO

  • Complete server software with web interface for managing Toniebox audio files locally
  • Detailed wiki covers setup, certificate patching, wifi chip access and reflashing
  • No hardware BOM — you bring the Toniebox, the server runs on any machine at home
  • Opening the Toniebox to reach the wifi chip voids the manufacturer's warranty
  • GPL-2.0 licence allows commercial and personal use with source disclosure
  • Community-maintained, active development with regular commits

Can I build this?

Printnothing required
Buya Toniebox if you don't already own one, otherwise nothing beyond standard soldering supplies if reflashing the chip
Toolsa machine to run Docker, basic soldering tools for chip access, a text editor for certificate patching
Skillscomfortable with Docker and command-line tools, basic soldering if reflashing the wifi chip, patience for step-by-step certificate work
Timean evening for setup and certificate patching, plus time to open the box and reach the chip if you choose that path
Cost$, dominated by the Toniebox itself if you don't already own one; the server software is free
SafetyStandard soldering precautions if accessing the wifi chip. Low-voltage electronics throughout; no mains work. Opening the box voids the warranty.

Build at your own risk. Projects involve tools, electronics and sometimes mains voltage — follow the creator’s safety notes.

Blu-ray drive, 10 Gbps hub and card reader in one boxPartner · Kickstarter
Blu-ray drive, 10 Gbps hub and card reader in one box

BluHub reads and burns Blu-ray/DVD/CD, adds USB-C, USB-A, SD/TF and 10 Gbps data — plug and play, grand-piano finish.

See the hub

Videos

Project Scheherazade: Liberating the Toniebox with TeddyCloud

No official project video; the reel output from Comparee Radar serves as the primary visual introduction

Gallery

https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud
https://github.com/toniebox-reverse-engineering/teddycloud

Start here

Navigation into the creator’s own docs — we don’t rewrite the guide, we route you to the source.

  1. 1.Read the project wiki to understand the certificate patching and server setup process(The wiki is the primary documentation; start there before touching the box)
  2. 2.Set up the TeddyCloud server using Docker on a machine that will stay running at home(The server must be reachable by the Toniebox on your local network)
  3. 3.Follow the certificate patching guide to generate and install the custom certificate(This step is required for the box to trust your server instead of the manufacturer's)
  4. 4.Open the Toniebox and access the wifi chip following the hardware guide if you need to reflash(This voids the warranty; only do this if you are comfortable with soldering and the risk)

Resources

Documentation, files and community threads for this build — we link straight to the original sources and never rehost the creator’s files.

KNOWN ISSUES

  • Opening the Toniebox to reflash the wifi chip voids the manufacturer's warranty permanently
  • Certificate patching must be done correctly or the box will refuse to connect to your server
  • Rushing the chip access can damage solder pads; follow the guide slowly and use proper tools
  • The server must stay running for the box to work; a turned-off machine means no audio
  • Not all Toniebox firmware versions are equally easy to patch; check compatibility first
  • Custom audio files must match the expected format or the box will reject them silently

Do I have to open the Toniebox?

Not necessarily. Some setups work by redirecting network traffic without hardware modification, but reflashing the wifi chip gives you full control and is the documented path for permanent local operation.

Can I still use the original cloud service after switching to TeddyCloud?

Not easily. Pointing the box at your own server is typically a one-way change unless you reflash the chip again to restore the original certificate.

What happens if the TeddyCloud server goes down?

The Toniebox will not play audio until the server is back online, because it asks the server what each figure should play. Keep the server machine reliable.

Is this legal?

Running your own server for a device you own is legal in most jurisdictions. Sharing copyrighted audio files is not, but using your own recordings or licensed content is fine.

Community builds

No community builds yet — be the first, we feature the best ones.

Discussion1

FROM THE COMPAREE TEAM

Opening the box voids the warranty, but it also means the box keeps working when the company's cloud doesn't. Would you make that trade for a child's toy?

CompareeTEAM12d ago

Practical notes from our verification: the repository URL was not provided in the payload, so we cannot confirm the current star count, last push date, or exact GitHub organisation structure. The Adafruit Blog post confirms the project exists and is GPL-2.0 licensed, and the reel output confirms detailed documentation including wifi chip access and certificate patching. The biggest practical hurdle is not the server setup — Docker makes that straightforward — it is the decision to open the box and the care required when reaching the wifi chip. If you are comfortable with that, the rest is methodical work through a well-documented wiki.

toniebox-reverse-engineering community

TeddyCloud is maintained by a community of developers and parents frustrated by the dependency on a manufacturer's cloud service for a children's toy. The project grew out of reverse-engineering work on the Toniebox protocol and has evolved into a complete local server replacement.

Star the project on GitHub

DISCLAIMER

  • Comparee is not the author of the projects featured here. All rights to each project belong to its creator — every page links to the original source, and we never host creators’ files.
  • Information is provided without warranty and may become outdated as projects evolve. Prices are indicative bands only — always check the creator’s parts list for current costs.
  • Building and operating any project is at your own responsibility. Protective equipment, safe workshop practice and compliance with local regulations are the builder’s responsibility.