Atlassian Rovo, Glean, Azure OpenAI Service vs Dify

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

The registry records Glean as available on vendor cloud or private cloud; it is scored here as enterprise SaaS.

The registry records Azure OpenAI Service as available on vendor cloud or private cloud; it is scored here as enterprise SaaS.

The registry records Dify as available on self-hosted or vendor cloud or private 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 — 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.

Covers your main objective (internal company search) and 2 of 3 secondary objectives (employee helpdesk, knowledge management).

Covers your main objective (internal company search) and 2 of 3 secondary objectives (employee helpdesk, knowledge management).

Covers your main objective (internal company search) and 1 of 3 secondary objectives (document Q&A).

Covers your main objective (internal company search) and 1 of 3 secondary objectives (document Q&A).

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. Headcount was not stated, so the size band could not be checked.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. Headcount was not stated, so the size band could not be checked.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. Headcount was not stated, so the size band could not be checked.

You stated no hosting preference, so no option is favoured on that basis. No hard restriction on where processing happens was stated. Headcount was not stated, so the size band could not be checked.

External data transfer: yes. No catalogue deployment names Atlassian Rovo, 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 Glean, 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 Azure OpenAI Service, 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: some. Computed from “Customer-support agent with knowledge base and handoff”, the catalogue deployment that names Dify and best matches this brief. Personal data leaves your premises for your own cloud tenancy ("Helpdesk / ticketing system"). You keep control of the account; the provider is a processor, so a DPA and a documented region apply.

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

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

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

We hold no fetched residency commitment for Dify. That is a question to put to the vendor, not an assumption to make about them.

We have fetched none of the four commitments for Atlassian Rovo: 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 Glean: 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 Azure OpenAI Service: 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 Dify: 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 Atlassian Rovo, 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 Glean, 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 Azure OpenAI Service, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief.

10–25 FDE-days to implement. Computed from “Customer-support agent with knowledge base and handoff”, the catalogue deployment that names Dify and best matches 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.

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.

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.

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 You run the model server yourself: GPU drivers, quantisation choice, memory headroom and restarts are all yours to own.

USD 3,100 – 23,000 — one-off — for Atlassian Rovo at this headcount. No catalogue deployment names Atlassian Rovo, 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 Glean at this headcount. No catalogue deployment names Glean, 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 Azure OpenAI Service at this headcount. No catalogue deployment names Azure OpenAI Service, 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 20,000 – 70,000 — one-off — for Dify at this headcount. Computed from “Customer-support agent with knowledge base and handoff”, the catalogue deployment that names Dify and best matches 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.

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

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

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

The registry files Dify as open source, so the interface, retrieval behaviour and the model behind it can be changed — subject to the licence, which is a fetched fact on its own page.

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.