RobotyUpdate
The phone could track the room and still miss the table
Our early iPhone placement checks exposed different AR failure states. A visible camera-free target editor kept one useful action available.
Building Roboty
Making affordable robots more capable and easier to use.
We’re building Roboty to help people do more with affordable robots, using familiar devices, AI where it helps, and tools that already work.
What we’re building
Roboty brings together the parts of a robotics experiment: setting a goal, trying an approach, understanding the result and deciding what to change. We’re building native controls and access for your own AI agent around the same tasks and results.
Our current development work starts with robot-arm simulations on a Mac, with an iPhone interface for setting up and reviewing experiments. Physical robot work has its own tests ahead.
See how Roboty worksWhat’s worth exploring
Affordable robot arms and existing robotics tools give us something concrete to build on. The question is how much more useful we can make them, and how much setup and effort we can take out of the experience.
More capability
Build on existing tools and test what affordable hardware can do.
Lower cost
Look at the whole cost: hardware, compute, setup and maintenance.
Less complexity
Make it easier to set up an experiment, understand a result and recover when something goes wrong.
From the blog
Building Roboty and sharing what we learn along the way.
The local model loaded. The simulated arm never moved.
Two local Qwen3.5 35B workflow sessions stopped before simulated Reach execution. Their failures matter, while reaching performance remains untested.
Deep dive
A cube's center can be in the tray while the cube is not
Our cube-to-tray evaluator checks the rotated object, support, release and settling. A worked edge case shows why a center-point test is too weak.