OpenBot robot platform for prototypes and small business use
OpenBot is an open-source Intel Labs project that turns an Android phone into a robot brain. How MILabs scopes and sets it up.
Updated 2026-01-27
What OpenBot is
OpenBot is an open-source robotics project published by Intel Labs on GitHub. It shows how an ordinary Android smartphone can serve as the main computer for a small wheeled robot. The phone supplies the camera, motion sensors and processing power, and a separate microcontroller board handles the motors. The code for the phone app and the robot body is public, so a team can read it, change it and run it on hardware of its own choosing. The project is aimed at research and education. It is not a hosted service and it has no business dashboard. Using it in a company means building and running the robot yourself, on equipment the business controls. For a small business, OpenBot is best understood as a prototyping kit for physical machines rather than a tool for office software. A team that enjoys hands-on work will get the most from it.
OpenBot in plain language
A wheeled robot needs three things to work: something that sees, something that decides, and something that turns decisions into movement. Hobby and prototype builds often buy each piece separately and join them with custom wiring. OpenBot asks how much of that job a commodity smartphone can already handle. A current handset packs an imaging system, a motion-sensing chip and enough compute to run compact recognition models, so it can take over the seeing and deciding roles. The rest of the machine stays deliberately simple. A low-cost controller board receives instructions and drives the wheels, so the moving parts can change without rewriting the intelligence.
Developers can train a detection model on a computer, convert it for the phone, and watch how the robot reacts to what it sees. Because the code is public, a team can read the control logic and change it, learning the reasoning behind each choice. That visibility is the main attraction. A group can follow every stage of the machine's behaviour, from camera frame to motor command, rather than relying on a sealed product. Nothing arrives finished, so the team assembles the chassis, sets up the phone and takes responsibility for how the parts behave together.
What businesses use it for
- Prototyping a small wheeled robot for a warehouse or yard trial before buying commercial equipment
- Testing whether a camera-based navigation task suits a particular floor, site or shelf layout
- Teaching staff or students the basics of sensors, motors and on-device machine learning
- Running internal demonstrations at trade shows, open days or client visits
- Collecting image and sensor data along a route to inform a later purchasing decision
Who it suits
- Operations leads who want to test a physical process before committing budget
- Teaching staff at schools or training providers building a hands-on robotics unit
- Small engineering teams that need a low-cost platform for experiments with vision-based driving
How MILabs sets it up
MILabs sets up an OpenBot project for a business by starting with the owner. Together we agree what the robot is meant to show or do, which site or space it will use, and what success looks like in plain terms. We then connect the parts the business already has, such as an Android phone, a chassis and a controller board, and check that they work together. Access is set for each person who needs it, including who can change the phone app, who can flash the controller and who can take the robot out of the test area. Before handover we agree who looks after the hardware, the phone software and any data the robot records. Nothing changes on the robot without the owner's written agreement.
Builds it fits
Industries it fits
OpenBot in practice
Inside a business, an OpenBot project usually looks like a bounded trial rather than a rollout. Someone picks a single movement problem, such as carrying a tote between two bays or following a painted line across a loading dock, and the team builds a small wheeled platform to test it.
The work splits into a few recognisable jobs. One person handles the physical side, fitting the chassis, checking the wiring and keeping the battery and motors in working order. Another handles the phone, which means loading the app, adjusting the camera view and deciding what the robot should do when the image is unclear. A third person, often from operations, watches the runs and writes down where the robot hesitated, drifted or stopped.
Each test session produces a small set of notes, and those notes shape the next change, so the robot improves through repeated short cycles rather than one large specification. The trial also brings forward questions a purchasing decision would otherwise hide. Does the floor reflect enough light for the camera to read it? Who is allowed to move the robot when a person walks into its path?
Frequently asked questions
- Where does OpenBot store data?
- OpenBot runs on hardware you choose, so its data stays on the phone, the controller and any computer you connect. The project is not a hosted service, which means no vendor account holds your recordings. Before a build starts, we agree where images and sensor logs are kept, who can open them and how long they are held. That plan is settled early, so the owner stays in charge of every recording.
- When is OpenBot the wrong choice?
- OpenBot suits a business that wants a prototype before a finished product. It fits small experiments on wheeled robots, and it is a good match for testing an idea on a shelf layout or a yard route. For office work such as email, invoices or bookings, a workflow tool like Zapier or Make serves better, and we are happy to say so at the start.
- Can my team use OpenBot without training?
- Yes, after a short walkthrough, staff can drive a finished robot with the phone app, but building or changing one takes more skill. Someone on the team should be comfortable installing an Android app, wiring a simple controller board and reading basic error messages. MILabs can run a first session with your team and leave written notes, so the knowledge stays in the business after the project ends.
- Can MILabs build on top of OpenBot?
- Yes, within the limits of an open robotics project. MILabs can adapt the phone app, write the logic that decides what the robot does, and pass its readings to a spreadsheet, dashboard or system your business already uses. Before work starts, we confirm with the owner what the robot is meant to do and which site and parts it will use.
- What does an OpenBot setup need from me?
- You need a named owner, a clear test area and a written agreement on what the robot should show or do. You also need an Android phone, a chassis and controller parts, or a decision to source them. Finally, name one person who will be available for questions during the trial and who can say whether the robot behaves as the business expected.
