Architecture
System design and structure
Architecture
How OctoMY™'s components fit together to create a distributed robotics platform.
Did You Know?
OctoMY™ is designed to work without any central server. Two nodes can communicate directly peer-to-peer, with optional Zoo servers only needed for NAT traversal across the internet.
Topics
| Topic | Description |
|---|---|
| Overview | High-level system architecture and design goals |
| Node types | Agent, Remote, Hub, and Zoo roles |
| Embedded/strategic barrier | Safety boundary for LLM integration |
| Component topology | Internal component structure |
| Security model | Cryptographic identity and trust levels |
| Node lifecycle | Launch, configuration, and activation |
| Communication system | Comms stack, carriers, channels, sessions |
| Platform | Cross-platform support strategy |
Key principles
OctoMY™'s architecture is built around:
- Distributed Operation - No central server required
- Peer-to-Peer Security - End-to-end encryption between nodes
- Graceful Degradation - Works despite network issues
- Modular Design - Components can be replaced or extended
- Local-First - Critical operations work without internet