I'm very curious - how do SingularityNET and CUDOS divide responsibilities in ASI:Cloud?

How do SingularityNET and CUDOS divide responsibilities in the development/launch of ASI:Cloud? Just curious.

Thank you for your question!

CUDOS provides and manages the GPU infrastructure; bare metal and VMs, orchestration, uptime, and network distribution. SingularityNET handles the inference backend, model catalog, and ongoing R&D (embedding optimization, mixture-of-experts routing, multimodal architecture). The ASI Alliance framework ties them together with unified authentication, billing, and APIs.