Why ReDo is Fully Open Source?

At ReDo, openness is not just a feature—it’s a foundation. We believe that creativity grows when ideas are shared, not locked away. The most powerful innovations of our time—whether in software, science, or art—have come from open communities that invite participation. That’s why every part of ReDo is designed to be open: from 3D models and mechanical designs to electronic schematics and firmware. It’s an ecosystem built for collaboration, not control.

Too many toy systems are walled gardens. You buy the toy, use it as intended, and hit a dead end the moment you want to do more. ReDo turns that model on its head. Want to tweak a servo design to fit a different toy form? You can. Want to write your own firmware for the controller or integrate new sensors? Go for it. With access to the full stack, you’re not limited to what we’ve imagined—you can take it further in any direction you choose.

This openness fuels a community of creators, tinkerers, educators, and young inventors. We’ve already seen users remix existing parts, build entirely new toys, and propose alternative approaches to solving design challenges. When users become contributors, the ecosystem grows faster and becomes more diverse. Innovation doesn’t come from a single company—it emerges from shared curiosity and collective problem-solving.

By making everything open, we’re also promoting transparency and trust. You can inspect how something works, improve it, or adapt it to your local context. This is especially important for educators, who need tools they can customize and understand deeply. It’s also crucial for families and makers who want to avoid vendor lock-in or learn what’s actually inside the toys they use. With ReDo, nothing is hidden behind proprietary walls.

Our mission is not just to build modular, programmable toys—it’s to spark a cultural shift. We want to raise a generation of inventors who expect openness, who are unafraid to take things apart, and who see creation as a shared, evolving process. Openness by design ensures ReDo is never static. It’s a living system, shaped by its users. And that’s the way it should be.

‍