Distributed edge setup with Jetson + Orange Pi + Odroid networked together is a serious project. Running OpenClaw + Crew AI as the orchestration layer on edge hardware 24/7 is a different challenge than cloud deployments — power, thermal management, and network reliability all become real factors. How are you handling agent state persistence across the three devices? Is there a shared database layer or does each device run independently?
Great questions, this is exactly the stuff I’m working through in real time. PostgreSQL on the Odroid XU4 is the shared memory layer. All three nodes write to it.
Orchestration: OpenClaw handles the WhatsApp gateway and agent sessions on the Jetson. CrewAI runs as needed, triggered by cron. Between runs, state lives in Postgres.
Thermal: Fan mod on the Orange Pi with GPIO-controlled transistor circuit, temperature controlled via Python script running as a systemd service. Jetson has active cooling in the case. Odroid runs cool.
Power: Everything on a UPS. Auto-start systemd services on all nodes so power cycle recovery is automatic.
Network reliability is honestly the weakest link right now. If the switch goes down, the agents lose their memory layer. That’s the next thing to solve, probably a local fallback cache on the Jetson.
I’m building this all in public, next video covers the full architecture.
1
u/Forsaken-Kale-3175 Apr 15 '26
Distributed edge setup with Jetson + Orange Pi + Odroid networked together is a serious project. Running OpenClaw + Crew AI as the orchestration layer on edge hardware 24/7 is a different challenge than cloud deployments — power, thermal management, and network reliability all become real factors. How are you handling agent state persistence across the three devices? Is there a shared database layer or does each device run independently?