Welcome to the rapyuta.io documentation, where you can find information and guides to help you learn about rapyuta.io and start exploring its features.
rapyuta.io is a platform that enables robotics solution development by providing the necessary software infrastructure and facilitating the interaction between multiple stakeholders who contribute to the solution development.
The software infrastructure can be seen as a collection of the following four layers and the facilitation is enabled by hardware and software catalogs.
Given the multi-domain and embryonic stage of the robotics industry, robotics solution developers face the following three challenges: lack of expertise, limited budget, and time. The pain points of the solution provider and gains using the project’s J-curve.
Our mission is to empower lives with connected machines. Machine - from robots, automation equipment, servers to network devices - connected and coordinated in a streamlined way to increase efficiency and reduce the human effort in 3K - kitanai (dirty), kiken (dangerous), kitsui (demanding) - work.
To make these machines more accessible, we follow the cloud robotics model defined as
Cloud Robotics is a model enabling self-service, elastic, and ubiquitous access to a shared pool of robotics resources with open interfaces.
This model is inspired by the cloud computing model is a broader definition of Cloud Robotics compared to the Cloud-connected Robotics definition by Kuffner.
Mell, Peter, and Tim Grance. “The NIST definition of cloud computing.”(2011).
Kuffner, James. “Cloud-Enabled-Robots” (2010)
Our journey on Cloud Robotics started with RoboEarth, an EU-funded project from 2010 to 2014, whose goal is to create an internet for robots, where robots could enjoy both a shared (via a common knowledge base) and an extended (via servers in a data center) brain.
The founding members of what would become Rapyuta Robotics made up the ETH Zurich team of the RoboEarth project. Our partners included six universities and the Dutch electronics giant Philips. For more details on our prior work, have a look at the following papers and videos: