The two providers at the top of the Multi-Cloud tag are Azure Arc and DoiT, and the Kin Score puts them 0.2 apart: Azure Arc 72.5, DoiT 72.3, both in the exemplar band. The Kin Score measures the public API surface, not the product and not the company, and on that surface these two are as close as a ranking gets. Then the Agent Readiness score puts them 48.6 apart, 25.5 against 74.1, and in opposite bands. A reader choosing between them is really asking a different question for each: who manages the machines outside my cloud, and who tells me what all of my clouds cost.
The business is not the same purchase. Azure Arc is Microsoft’s hybrid and multi-cloud management service. It projects servers and Kubernetes clusters running outside Azure into Azure Resource Manager, so they can be governed, patched, extended and monitored with Azure tooling, and its REST surface is the Hybrid Compute and Hybrid Kubernetes resource providers on management.azure.com. DoiT sells DoiT Cloud Intelligence, a FinOps platform that unifies cost, usage and savings data across AWS, Google Cloud, Azure, Kubernetes and more than forty other clouds and SaaS providers. Both records show a freemium, self-serve access model with a try-now path and no trial. Multi-Cloud is the tag they share; one is in it to control infrastructure, the other to account for it.
The APIs. Azure Arc publishes 18 API pages carrying 79 operations, every one of them on management.azure.com: the Machines API, the Connected Clusters API, the Extensions API and the Machine Run Commands API among them, plus 51 JSON Schemas and three Postman collections. DoiT publishes 49 API pages and 250 operations on api.doit.com, the resource groups of one Platform API contract — the Anomalies API, the Budgets API, the Allocations API, the Ava API for its AI assistant — and a first-party remote MCP server at mcp.doit.com listing 90 tools. Neither provider’s contracts were derived by us. Azure Arc’s MCP, skills and agentic-access artifacts were, and its agentic-access profile classifies 7 operations from one source file against 79 on its pages, so we are not setting its acting count next to DoiT’s.
The experience, facet by facet. Azure Arc wins three facets and DoiT two, with discoverability tied at 75.0. The widest delta is operational transparency, 86.8 to 61.8 for Azure Arc: status, changelog, rate limits and the operational signals a team needs to run against an API in production, where Microsoft’s machinery shows. Azure Arc also takes access clarity 81.6 to 76.3 and contract governance 22.0 to 18.2, though at 22.0 and 18.2 governance is a weakness both share rather than a win. DoiT takes contract quality 63.5 to 56.4, which is the heaviest facet at 0.25, and developer ergonomics 73.8 to 73.2. On the six weighted facets alone Azure Arc leads, 66.5 to 63.6. The conditional layers then move DoiT by 8.7 and Azure Arc by 6.0, and most of that difference is the upsert check, where DoiT scores 61.1 to Azure Arc’s 22.2. Both sit under the same Horizontal regulatory regime, so the comparison is over the same facet set. Azure Arc’s 0.2 lead is a 2.9-point base lead that DoiT nearly erases on that one conditional check.
Agent readiness is where they stop being close. DoiT is agent-native at 74.1; Azure Arc is agent-aware at 25.5. Read the dimensions and the gap is not one thing, it is nine. DoiT has a verified MCP server, verified idempotency, documented reversibility, a dry-run mode, a described event surface, served delegated identity, verified protected resource metadata, dynamic client registration, and partial examples in its OpenAPI. Azure Arc has none of those on its record. What it does have is a bearer-auth contract, a verified rate-limit signal and error semantics we derived. The agent-native band is gated on idempotency and a stable error envelope, not only on the score, and DoiT clears both gates verified. That is not an accident of a FinOps company; the rest of the Multi-Cloud tag lights idempotency at 8.9%.
The verdict, with the conditions on it. If the job is operating servers and clusters that live outside Azure from inside Azure, Azure Arc is the API, and its surface is the more transparent one to run against — a Microsoft resource provider with the operational signals that come with it. If the job is putting an agent in front of cloud spend across many providers, DoiT is the clearer choice by a wide margin: it ships the MCP server, the identity plumbing and the safety signals an agent needs, from the company itself. What would move Azure Arc’s agent number is mostly what already exists elsewhere in Azure — a first-party MCP surface, idempotency and reversibility documented on the operations that create and delete machines and extensions, and protected resource metadata for the OAuth it already uses. What would move DoiT’s Kin Score past it is the facet both of them are weakest on: contract governance, at 18.2, is a versioning and lifecycle story it has not yet told.