Azure AI Document Intelligence, GitHub Copilot, Kimi Open Platform vs Cursor

The registry records Azure AI Document Intelligence as available on vendor cloud or private cloud or on-premise enterprise; it is scored here as enterprise SaaS.

The registry records GitHub Copilot as available only on vendor cloud; it is scored here as enterprise SaaS.

The registry records Kimi Open Platform as available only on vendor_api; it is scored here as a model vendor's API.

The registry records Cursor as available only on vendor cloud; it is scored here as enterprise SaaS.

For this brief — confidential documents — enterprise SaaS is conditional: worth it only if the conditions in the options section hold. Change the brief and this verdict changes.

For this brief — confidential documents — enterprise SaaS is conditional: worth it only if the conditions in the options section hold. Change the brief and this verdict changes.

For this brief — confidential documents — a model vendor's API is a strong alternative. Change the brief and this verdict changes.

For this brief — confidential documents — enterprise SaaS is conditional: worth it only if the conditions in the options section hold. Change the brief and this verdict changes.

Built for OCR, invoice extraction, data extraction, document classification, which does not include AI coding assistant.

Covers your main objective (AI coding assistant).

Kimi Open Platform is a platform for running a model you choose, not a product built for one job, so there is no use-case overlap to measure — what it does depends on what you build on it. The fit that can be assessed is the deployment's, in the rows below.

Covers your main objective (AI coding assistant).

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. This is a vendor-operated service. Your cloud account does not determine where it runs; confirm the vendor’s data processing and integration with your existing systems.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. This is a vendor-operated service. Your cloud account does not determine where it runs; confirm the vendor’s data processing and integration with your existing systems.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. The model runs through the vendor’s API. Your application may use your existing cloud, but the vendor’s processing location and terms need separate review.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. This is a vendor-operated service. Your cloud account does not determine where it runs; confirm the vendor’s data processing and integration with your existing systems.

External data transfer: yes. No catalogue deployment names Azure AI Document Intelligence, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Confidential content leaves your control on the Employees → Vendor assistant (web and desktop clients) link.

External data transfer: yes. No catalogue deployment names GitHub Copilot, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Confidential content leaves your control on the Employees → Vendor assistant (web and desktop clients) link.

External data transfer: yes. No catalogue deployment names Kimi Open Platform, so this is read from “Agent workflow on a model vendor’s API”, the best-matching a model vendor's API deployment for this brief. Confidential content leaves your control on the Tools + retrieval (your APIs and data) → Vendor model API link.

External data transfer: yes. No catalogue deployment names Cursor, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Confidential content leaves your control on the Employees → Vendor assistant (web and desktop clients) link.

We have fetched a supported-countries page for Azure AI Document Intelligence, which says where the product may be bought — not where content is processed or stored. No residency commitment has been read, so the residency question is unknown. The vendor is headquartered in United States, which is where a transfer question starts, not where it ends.[1]

We hold no fetched residency commitment for GitHub Copilot. That is a question to put to the vendor, not an assumption to make about them. The vendor is headquartered in United States, which is where a transfer question starts, not where it ends.

We hold no fetched residency commitment for Kimi Open Platform. That is a question to put to the vendor, not an assumption to make about them. The vendor is headquartered in China (mainland), which is where a transfer question starts, not where it ends.

We hold no fetched residency commitment for Cursor. That is a question to put to the vendor, not an assumption to make about them. The vendor is headquartered in United States, which is where a transfer question starts, not where it ends.

Published and fetched: data processing agreement, subprocessor list. Still open: training on customer data, zero retention option — ask the vendor.[2][3]

Published and fetched: data processing agreement, subprocessor list. Still open: training on customer data, zero retention option — ask the vendor.[4][5]

We have fetched none of the four commitments for Kimi Open Platform: data processing agreement, subprocessor list, training on customer data, zero retention option. Each is a question for the vendor, and until it is answered it is unknown rather than absent.

We have fetched none of the four commitments for Cursor: data processing agreement, subprocessor list, training on customer data, zero retention option. Each is a question for the vendor, and until it is answered it is unknown rather than absent.

4–12 FDE-days to implement. No catalogue deployment names Azure AI Document Intelligence, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief.

4–12 FDE-days to implement. No catalogue deployment names GitHub Copilot, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief.

8–22 FDE-days to implement. No catalogue deployment names Kimi Open Platform, so this is read from “Agent workflow on a model vendor’s API”, the best-matching a model vendor's API deployment for this brief.

4–12 FDE-days to implement. No catalogue deployment names Cursor, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief.

The vendor runs the service. Your standing work is access control, the policy staff work under, and re-reading the contract and subprocessor list when they change — not patching or capacity.

The vendor runs the service. Your standing work is access control, the policy staff work under, and re-reading the contract and subprocessor list when they change — not patching or capacity.

You own the identity integration and joiner/leaver process, the connectors and their credentials, operating-system patching and backups. Assessed difficulty 3/5 is the shape of that work; someone has to hold it after go-live.

The vendor runs the service. Your standing work is access control, the policy staff work under, and re-reading the contract and subprocessor list when they change — not patching or capacity.

2/5. Starting point 1/5: a vendor product, configured rather than installed. +0.5 Single sign-on adds an identity provider, group-to-role mapping and a joiner/leaver process to the deployment.

2/5. Starting point 1/5: a vendor product, configured rather than installed. +0.5 Single sign-on adds an identity provider, group-to-role mapping and a joiner/leaver process to the deployment.

3/5. Starting point 2/5: software you install, run and keep running on your own machines. -0.5 The model runs on the vendor’s infrastructure: there is no capacity planning, no GPU driver, no model upgrade window and no failover for you to design.

2/5. Starting point 1/5: a vendor product, configured rather than installed. +0.5 Single sign-on adds an identity provider, group-to-role mapping and a joiner/leaver process to the deployment.

USD 3,100 – 23,000 — one-off — for Azure AI Document Intelligence at this headcount. No catalogue deployment names Azure AI Document Intelligence, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Licences are not in that figure: no per-seat price has been read from the vendor’s own pricing page, so the software line is excluded from the total rather than guessed. Read it as implementation only.

USD 3,100 – 23,000 — one-off — for GitHub Copilot at this headcount. No catalogue deployment names GitHub Copilot, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Licences are not in that figure: no per-seat price has been read from the vendor’s own pricing page, so the software line is excluded from the total rather than guessed. Read it as implementation only.

USD 6,100 – 43,000 — one-off — for Kimi Open Platform at this headcount. No catalogue deployment names Kimi Open Platform, so this is read from “Agent workflow on a model vendor’s API”, the best-matching a model vendor's API deployment for this brief.

USD 3,100 – 23,000 — one-off — for Cursor at this headcount. No catalogue deployment names Cursor, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief. Licences are not in that figure: no per-seat price has been read from the vendor’s own pricing page, so the software line is excluded from the total rather than guessed. Read it as implementation only.

Azure AI Document Intelligence is a vendor product: you configure what the vendor exposes — policies, connectors, retention settings — and nothing below that line.

GitHub Copilot is a vendor product: you configure what the vendor exposes — policies, connectors, retention settings — and nothing below that line.

Kimi Open Platform is a vendor product: you configure what the vendor exposes — policies, connectors, retention settings — and nothing below that line.

Cursor is a vendor product: you configure what the vendor exposes — policies, connectors, retention settings — and nothing below that line.

8 issues spotted for this brief, 0 of them legal requirements; 0 carry a quote from the instrument they rest on. Leading with: Confidentiality duties bind independently of data protection law.

8 issues spotted for this brief, 0 of them legal requirements; 0 carry a quote from the instrument they rest on. Leading with: Confidentiality duties bind independently of data protection law.

8 issues spotted for this brief, 0 of them legal requirements; 0 carry a quote from the instrument they rest on. Leading with: Confidentiality duties bind independently of data protection law.

8 issues spotted for this brief, 0 of them legal requirements; 0 carry a quote from the instrument they rest on. Leading with: Confidentiality duties bind independently of data protection law.