Interoperable by design
A skill is written against the module's eyes and ears, not any one platform's SDK. It doesn't need rewriting to ride something new.
Symbian is a small, interoperable module you attach to a robot, a drone, a vehicle, or something that never moves at all. It sees what you see, works out what matters, and talks to you about it — amplifying whatever host it's riding, without changing what that host already does best.
A quadruped can cross rubble. A drone can hold position in wind. A car can keep itself in a lane.
None of them know what they’re looking at, where they are, or what you want. The hard problems got solved. Awareness never arrived.
One small module, riding on top of what already works. Eyes, ears and a voice for anything you already own.
A capability on Symbian is called a skill, and skills do not belong to a platform. The same skill runs whether the module is riding a warehouse quadruped, clipped to a motorcycle, or sitting on a shelf watching a doorway. You do not buy a version for each machine. You buy it once and it follows the module.
host 01 · warehouse quadruped
It is the way your headphones follow you between your phone and your laptop, applied to machines that cost a hundred times more.
A skill is a capability the module can perform — seeing, reasoning, talking. It belongs to the module, not to any platform.
A skill is written against the module's eyes and ears, not any one platform's SDK. It doesn't need rewriting to ride something new.
The robot keeps doing exactly what it was built to do. Symbian adds perception on top and makes the platform more capable.
A quadruped today, a motorcycle tomorrow, a shelf watching a doorway after that. The module doesn't need to know what it's riding.
We're not a robotics company. We collaborate with the companies who spent a decade solving locomotion, and co-build where it helps both of us.
The host keeps its strengths. We add the senses.
A sphere with a visor across the front. Behind the visor, the cameras. A microphone to hear you, a speaker to answer. No mouth, because the speaker is the mouth.
Where the thinking happens. Symbian carries almost no intelligence of its own — the reasoning, the model calls and the retrieval all run on Teepin.
A capability written once against the module's sensors, not against any single platform's SDK. That is what makes it interoperable.
Settles level under gravity. No firmware, no calibration, no stabilisation software. Motorised only if a host proves it needs it.
§ 08 · What we don't build
Symbian has no motors that move it, no chassis, no drivetrain, and no opinion about how your host gets from one place to another. The only moving part we care about is the gimbal that keeps the cameras level.
A platform that spent a decade solving locomotion doesn't need us to solve it again, and we're not going to try. Symbian attaches, it doesn't replace — and every skill we build is built to make the host underneath it more capable, not to make the host optional.
No legs, no rotors, no chassis, no drivetrain. The physical machine stays entirely the platform's work, and we're not trying to take it from them.
A skill adds sight, hearing and a voice on top of what a host already does. It never asks a platform to change how it moves, balances, or flies.
The same interoperable skill runs across every platform we work with. No partner gets a worse version because they came second.
Where a platform brings the customer, the platform takes its share, the way app stores do. We're a partner in the transaction, not a competitor to it.
If a platform wants a skill that doesn't exist yet, we'd rather build it together than guess at it alone.
It doesn’t exist yet. There’s a prototype and a small team. No launch date, no price, no waitlist theatre.
Leave an email and we’ll tell you when there’s something worth looking at — and if you build robots, drones or anything with a host, tell us that too. We’d rather co-build than guess.
SYMBIAN