We deploy humanoid robots and robot dogs for European industry
Robotoplus is a European robotics integrator. We bring humanoid robots and robot dogs into real production environments and stay involved once they are there.
What we are, and what we are not
Robotoplus does not build robots. AGIBOT builds them, and we are their appointed distributor for Bulgaria and Romania. It is worth saying plainly, because a page like this one is usually where the distinction gets blurred.
What we build is the part between a machine and a working process: the application layer, the integration with whatever already runs on your floor, the safety boundary, operator training, and the service arrangement afterwards. Hardware is one component of that. It is the expensive component and the one people fixate on, but a humanoid that cannot be told what to do in the vocabulary of your process is an expensive demonstration.
The split also decides who you call. A failed joint is a manufacturer question and it goes to them through a named channel rather than into a queue. A robot that picks the wrong part off a belt is ours, and there is nobody for us to point at. Buying through an unaffiliated dealer tends to leave that line undrawn, and where it falls becomes clear only after something has already gone wrong.
Mission and vision
Mission
Our mission is simple: take robot hardware, add software our own engineers write for your task, and stay with it long after it's deployed.
Vision
A generation of machines that adapt to workplaces designed for people, instead of workplaces rebuilt around machines.
How we work
Where the data sits
The application layer runs on your own network. Where a component talks back to a manufacturer service, as the companion app does, we say so before you order rather than after.
Qualify, then quote
The assessment is billed as its own work, so it is free to end in a no. When it does, the answer is usually a fixed arm, a conveyor or a different year.
Safety has an owner
A defined working envelope, a rule about who may enter it while the machine is live, and one name on your side against the sign-off. Left late, it is what stops a deployment that already works.
Published figures only
Where a specification comes from is recorded, and it is not always the manufacturer. Where AGIBOT publishes a parameter table we use it. Where it does not, the figures come from the reseller listing this catalogue was built on, and the product page says so under its own table rather than letting you assume otherwise.
Why AGIBOT, and what we turn down
- AGIBOT publishes parameter tables.
- That reads like a low bar until you look at how much of this field communicates through video, where a figure you cannot check is indistinguishable from a figure that does not exist. A published figure can be held against the machine in front of you, and the comparisons on our category pages are built from published figures rather than from claims. Not every figure here has a manufacturer table behind it. Where it does not, the product page says so under its own table.
- The software is inspectable too.
- Where a platform has a published SDK, its product page links the repository and names the licence, because a permissive licence and a non-commercial one are very different propositions for a company planning to build on top. Where a repository ships code with no licence file at all, as the D1 Max repository does, the page says that as well. An unlicensed repository is a question for your legal and engineering teams, not a footnote.
- One manufacturer.
- A wheeled torso, bipedal platforms, quadrupeds and dexterous hands come from one maker. One contract, one spares channel and one named contact, whichever machine you deploy second.
- What we turn down:
- work a fixed industrial arm does more cheaply and more repeatably, tasks a conveyor and a sensor solve for a fraction of the cost, anything where a person's safety would depend on the robot behaving correctly rather than on a guard or an interlock, and demonstrations whose real purpose is a photograph. The first two come up often and the answer is a short conversation. The last two are not a matter of preference.
The order this usually happens in
Qualify
We walk the process with you and decide together whether a humanoid is the right tool. This is the step that most often ends with us saying no, and it is the cheapest place for that to happen.
Scope
Cycle times, payloads, tolerances, floor conditions and the safety boundary are written down before anything is ordered. Where a figure is a guess, it is labelled as a guess.
Proof of concept
One task, on your floor, on a rental unit, measured against the criteria set during scoping. A pilot whose criteria are agreed afterwards always succeeds and tells you nothing.
Engineer
Our engineers write the application layer on ROS 2 and connect it to whatever holds your orders, whether that is a PLC, a warehouse system or a spreadsheet somebody maintains. This is where the schedule actually goes.
Deploy
Installation, the safety sign-off, and two or three operators who can start it, stop it, clear a fault and recognise when to call. Handover is a document, not a demonstration.
Support
Spares, service and application changes as the process moves. Where nobody on site owns the machine it quietly falls out of use, which is why the handover names someone.