On 5 November 2026, Moonshot AI announced Kimi Hosted Agents, a service that sells the least exciting component of the AI stack: the runtime. The company is taking the Harness, the execution framework that actually keeps an agent alive while it works, and offering it as a cloud service. Teams no longer build or maintain their own orchestration framework; they get a 7x24 hosted environment ready for long-horizon tasks and multi-agent collaboration.
For the past two years the commercial story of Chinese large-model companies has been about tokens: the longest context, the cheapest inference, the flashiest agent demo. Kimi Hosted Agents moves one rung up that ladder, from selling model capability to selling the environment in which the capability runs. A hosted Harness means the state, retries, tool calls, sandboxing, scheduling and failure recovery are somebody else's operational burden. If you have watched a promising agent demo collapse after eleven minutes because a session expired, you understand why uptime is a product.
The deflating part is that AWS and Alibaba Cloud already offer comparable managed services, and they arrive with deeper enterprise relationships and far more infrastructure depth. Moonshot's advantage is the native coupling between its own models and its own agent framework. Its weakness is that it does not own the cloud beneath it. As National Business Daily noted, once the value chain moves from tokens to managed services, competition shifts from benchmark scores to ecosystem thickness and radius of trust.
Key points
- Announced 5 November 2026 by Moonshot AI, the company behind Kimi
- Product: a cloud-hosted agent Harness with a 7x24 always-on environment
- Designed for long-horizon task execution and efficient multi-agent collaboration
- No self-built or self-maintained runtime required
- Competitive caveat: AWS and Alibaba Cloud already offer comparable managed services
- Broader shift: from selling tokens to selling managed services; from benchmark scores to ecosystem depth
Read the full story on threerouter: https://www.threerouter.com/blog/345
Top comments (0)