SGLang, Dify, Langfuse vs Onyx

The registry records SGLang as available on self-hosted or private cloud or on-premise enterprise; it is scored here as self-hosted.

The registry records Dify as available on self-hosted or vendor cloud or private cloud; it is scored here as enterprise SaaS.

The registry records Langfuse as available on self-hosted or vendor cloud or private cloud; it is scored here as enterprise SaaS.

The registry records Onyx as available on self-hosted or vendor cloud or private cloud; it is scored here as enterprise SaaS.

For this brief — confidential documents — self-hosted 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.

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.

Built for local LLM, private LLM, which does not include AI customer-support agent.

Covers your main objective (AI customer-support agent) and 3 of 3 secondary objectives (internal company search, document Q&A, private company ChatGPT).

Covers your main objective (AI customer-support agent) and 2 of 3 secondary objectives (internal company search, private company ChatGPT).

Covers your main objective (AI customer-support agent) and 2 of 3 secondary objectives (internal company search, 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: some. No catalogue deployment names SGLang, so this is read from “Customer-support agent with knowledge base and handoff”, the best-matching self-hosted deployment for 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.

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.

External data transfer: yes. No catalogue deployment names Langfuse, 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 Onyx, 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.

Self-hosted: the content stays wherever you run the server, so residency is a property of your own infrastructure rather than a vendor commitment.

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 hold no fetched residency commitment for Langfuse. That is a question to put to the vendor, not an assumption to make about them. The vendor is headquartered in European Union, which is where a transfer question starts, not where it ends.

We hold no fetched residency commitment for Onyx. 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.

Run on your own infrastructure, so the vendor questions apply only to whatever you still buy. We hold none of the four commitments for this subject, and for a self-hosted deployment none of them is required.

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.

We have fetched none of the four commitments for Langfuse: 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 Onyx: 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.

10–25 FDE-days to implement. No catalogue deployment names SGLang, so this is read from “Customer-support agent with knowledge base and handoff”, the best-matching self-hosted 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.

4–12 FDE-days to implement. No catalogue deployment names Langfuse, 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 Onyx, so this is read from “Enterprise SaaS assistant with governance controls”, the best-matching enterprise SaaS deployment for this brief.

You own GPU drivers and the model server, 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.

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.

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.

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.

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.

USD 20,000 – 70,000 — one-off — for SGLang at this headcount. No catalogue deployment names SGLang, so this is read from “Customer-support agent with knowledge base and handoff”, the best-matching self-hosted deployment for this brief.

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.

USD 3,100 – 23,000 — one-off — for Langfuse at this headcount. No catalogue deployment names Langfuse, 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 Onyx at this headcount. No catalogue deployment names Onyx, 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.

The registry files SGLang 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.

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.

The registry files Langfuse 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.

The registry files Onyx 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.

7 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.