-
Notifications
You must be signed in to change notification settings - Fork 61
Home
Guillaume Binet edited this page Jan 6, 2026
·
18 revisions
Copper is a deterministic robotics runtime written in Rust. Think of it as a "game engine for robots": describe your system declaratively, compile the schedule, and run deterministically from cloud simulation down to embedded controllers.
Why Copper
- ⚡ Sub-microsecond latency with a zero-alloc, data-oriented runtime.
- ⏱️ Deterministic replay for debugging and certification.
- 🧠 Interoperable with ROS 2 via bridges.
- 🪶 Runs anywhere from x86 servers to bare metal.
Ready to get started? Check out the README or jump into Build and Deploy a Copper Application.
| Topic | What you'll get |
|---|---|
| 🚀 Build and Deploy a Copper Application | Project structure, build artifacts, and deployment flow. |
| ⚙️ Copper Configuration file Reference | The RON schema for tasks, messages, and connections. |
| 🗺️ Copper Configuration and Mission Visualization | Render task graphs and mission definitions. |
| 🧭 Copper Tasks lifecycle overview | How tasks run, pause, and serialize state. |
| 🧩 Modular Configuration | Split big configs into reusable chunks. |
| 🌉 Copper Bridge concept | Link Copper to external systems and protocols. |
| 🔧 Baremetal Development | Running Copper as a bare-metal runtime. |
| 🖥️ Supported Platforms | Desktop, mobile, and embedded targets. |
| Task Lifecycle | Build and Deploy | Missions |
|---|---|---|
- 🧱 List of available components
- 📚 API Documentation on docs.rs
- 🧪 Bleeding edge API Documentation (master branch)
- 📦 Main crate on crates.io
- 💻 Source code on GitHub
- 🛠️ Contributing guide
Start
Concepts
- Copper Configuration and Mission Visualization
- Copper Tasks lifecycle overview
- Copper Bridge concept
- Modular Configuration
Embedded
Reference
External