Analysis updated 2026-07-17 · repo last pushed 2024-09-23
Coordinate sensors, motors, and AI models on a robot arm using a shared runtime instead of custom glue code.
Deploy a fleet management system where robots share a core framework but run custom robot-specific logic.
Build a cloud-based AI service that multiple robots connect back to for tasks like route planning.
Integrate AimRT alongside an existing ROS2, HTTP, or gRPC setup without rebuilding your whole robot stack.
| peng-zhihui/aimrt | 1786329860/deep-teach | bjarneo/quickshell | |
|---|---|---|---|
| Stars | 88 | 88 | 88 |
| Language | — | — | QML |
| Last pushed | 2024-09-23 | — | — |
| Maintenance | Stale | — | — |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Designed for real robot deployments spanning device, edge, and cloud, so setup involves multiple infra components.
A lightweight C++ runtime framework that coordinates a robot's sensors, motors, and AI models, letting developers deploy the same core software on the robot, an edge server, or the cloud.
Stale — no commits in 1-2 years (last push 2024-09-23).
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.