Jibo.Cloud
Summary
Jibo.Cloud is the replacement cloud layer for OpenJibo.
Its job is to restore the hosted services that physical Jibo devices still expect, while also becoming the bridge into a modern .NET runtime and future capabilities.
Current Strategy
The project is deliberately split into two roles:
node/Reverse-engineering oracle, discovery server, fixture source, and rapid protocol lab.dotnet/Stable hosted implementation intended for Azure deployment and long-term maintenance.
The Node server remains valuable, but it is no longer the target production architecture.
First Production Goal
The first milestone is a stable hosted cloud that can support:
- token and session issuance
- account and robot identity flows needed for startup
- required HTTPS
X-Amz-Targetoperations - required WebSocket listen and proactive flows
- basic media and update metadata handling
- normalized handoff into OpenJibo runtime contracts
Hosting Direction
The hosted deployment target is Azure:
- Azure App Service with WebSockets enabled
- Azure SQL as the system of record
- Azure Blob Storage for upload and update artifacts
- Azure Key Vault for secrets and certificates
- Application Insights for telemetry and diagnostics
Human-facing entry points will live on domains such as:
openjibo.comopenjibo.ai
Robot traffic may still arrive using legacy hostnames routed to the OpenJibo service.
Recovery Strategy
The first supported device path is:
RCM + controlled DNS/TLS patching + hosted OpenJibo cloud
OTA remains important, but it is a later simplification layer after the hosted cloud is stable on real hardware.