OpenCastor
The universal runtime for embodied AI
OpenCastor connects model providers, safety systems, swarm orchestration, messaging channels, and robot drivers through one runtime and one config surface.
Overview and Mission
Problem
Robotics teams often rebuild control stacks for each hardware kit, provider, and channel. That fragmentation slows delivery and makes safety and operations inconsistent.
OpenCastor addresses this by standardizing runtime behavior behind RCAN-based configuration and a shared safety and orchestration model.
Mission
Provide a single, production-capable runtime where embodied AI systems can integrate models, hardware, and channels without rewriting core control logic.
The practical goal is faster integration with safer operations and clearer operator tooling.
Architecture Summary
Runtime Core
- - RCAN config-driven runtime composition
- - Provider routing and fallback pathways
- - Driver abstraction for mixed robot hardware
- - API and dashboard operations surfaces
Safety and Operations
- - Safety enforcement and emergency control pathways
- - Auditability and runtime telemetry
- - Fleet/swarm-aware coordination surfaces
- - Setup, diagnostics, and operator runbooks
Compatibility Highlights
Hardware
Drivers and presets for edge robots, STEM kits, and custom boards.
- - ESP32 and Arduino pathways
- - LEGO and VEX class educational kits
- - OAK depth camera and LiDAR/IMU pathways
Providers and Models
Multi-provider, multi-model operation through one runtime interface.
- - Anthropic, OpenAI, Google, Groq, OpenRouter
- - Ollama, llama.cpp, MLX, ONNX, Vertex pathways
- - VLA and embedding provider integrations
Agent and Channel Surface
Operations from dashboard, APIs, messaging, and SDK clients.
- - Swarm/fleet orchestration pathways
- - Messaging and command channel integrations
- - JavaScript SDK and MCP entrypoints
Timeline Snapshot
February 16, 2026: Repository created.
February 17, 2026: First commit, first tag, first release (v2026.2.17.3).
February 18-20, 2026: Installer and setup stabilization sprint.
February 21-23, 2026: Swarm, safety, provider, hardware, and SDK integration burst.
February 24-26, 2026: Reliability hardening, release process tightening, and tutorial expansion.
Building with OpenCastor?
I can help scope integrations across hardware, providers, safety controls, and deployment workflows.