Langdock vs nele.ai

Langdock

The terms state that neither Langdock nor the model providers it engages may use customer content to train models, admins can set a chat-retention period with deletion behaviour documented for chats, agent files and folders, and Azure-hosted models run with zero-data-retention abuse monitoring, on top of an automatically concluded DPA and published ISO 27001 and SOC 2 Type II certificates. The abuse-monitoring and retention detail is stated for the Azure models only, so I cannot credit the per-provider accounting that would score higher.

nele.ai

The privacy policy instructs the AI providers that user inputs may not be stored with them or used for learning, though only subject to the functions those providers make available, and it states logfiles are kept at most 30 days before deletion or anonymisation with personal data deleted once the purpose ends. We found no public information naming the model providers, stating retention periods for chats and files, or confirming a data processing agreement for business customers — which my compliance team would demand before connecting ticket data.

Langdock

The platform is model-agnostic with 40-plus models, EU-only inference is the default with global-deployment models an explicit customer choice whose data at rest still stays in EU data centres, hosting runs on Azure in Frankfurt with the EU Data Boundary, and bring-your-own-key plus own-cloud or on-premises deployment are documented — the latter from 5,000 seats, far beyond my forty. Per-model inference regions are not published, so an admin cannot verify each model's processing location from the public pages.

nele.ai

User inputs are processed on the vendor's own servers at a stated German location, with Microsoft Azure in Frankfurt and Hetzner in Germany named for hosting. We found no public information on which AI models sit behind the assistant or where their inference runs, so I cannot tell whether any prompt ever leaves the EU.

Langdock

SAML 2.0 single sign-on with any identity provider and SCIM ship on the business plan, role-based access control and IP restrictions exist, retrieval mirrors the source tool's permissions one-to-one, and the governance console lets admins review, approve, flag or disable agents with automated compliance checks on every new version, plus usage analytics exportable as CSV or via API. I found no public information on exportable audit logs of admin and user actions, which is the first thing my security team will ask for.

nele.ai

The captured pages include a page on single sign-on with SAML 2.0 and an administrator section on knowledge bases, and the privacy policy describes user account registration — a start for onboarding forty agents. We found no public information on roles and groups, automated provisioning, audit logs or usage reporting.

Langdock

MCP support is first-class — a directory of 79 verified, officially operated remote servers, custom MCP servers with OAuth or API-key auth, an apps extension with a JavaScript SDK, agent-to-agent protocol, a ServiceNow reference implementation for creating records and Zapier reaching 7,000-plus apps — alongside Outlook and Excel add-ins and agents usable from Slack and Teams. I found no public information on connector sync behaviour, on source citations for grounded answers, or on contact-centre or telephony integration, and the last is what my queue lives on.

nele.ai

Captured pages describe knowledge bases with retrieval-augmented generation and their administration, so some knowledge layer exists. We found no public information on connectors to ticketing or CRM systems, an API, sync behaviour, or how answers cite their sources — the connections my order and ticket workflows would depend on.

Langdock

Agents attach skills, integration actions, workflows and subagents, act under human confirmation configured per action node with approve, reject and form input steps, run on triggers and schedules, and ship through a build-and-test toggle with versioned publication, automated governance checks on each version and per-agent analytics and cost visibility, plus published disclaimers and EU AI Act use limits. Before I go live I need evaluation against a test set and handover of a conversation to a human with its full context; I found no public information on either.

nele.ai

We found no public information on agent capabilities on the captured homepage, data-protection and terms pages — nothing on multi-step tasks, actions in ticketing or order systems, handover to a human with full context, or testing and evaluation before go-live. I cannot judge an AI agent for my contact-centre queues from this.

Langdock

Langdock GmbH of Berlin contracts under German law with Berlin as the place of jurisdiction, hosts on Microsoft Azure in Frankfurt with the EU Data Boundary, defaults to EU-only processing with transfers outside the EU only on the customer's instruction, and publishes its subprocessors with locations — OpenAI Ireland, Google Cloud and AWS in the EU — with a DPA concluded automatically and ISO 27001 and SOC 2 certificates downloadable. Sentry in the United States processes error and diagnostic data under Data Privacy Framework and standard-clause safeguards, and I found no public information on the company's ownership, so I cannot call it sovereign end to end.

nele.ai

The vendor is a German company registered at the Gießen court with a stated German server location, and it lists subprocessors with locations — Microsoft Azure in Frankfurt, Hetzner and Brevo in Germany — while US payment and website services are covered by the Data Privacy Framework and standard contractual clauses. For an AI product the model provider is the decisive subprocessor, and we found no public information naming it; the privacy policy says only that inputs are not sent directly to the AI providers.

Langdock

Seat prices are public — €23.20 standard and €99.00 Business Max per user per month excluding VAT with 20% saved on annual billing — models are included with no usage-based costs for chat and agents, workflow tiers carry run counts (2,500 included, €449.00 per workspace per month for 40,000 runs) and API token rates are published per model. The enterprise tier is "Custom. Contact us", the fair-use quantities behind "5x more usage than Standard seat" are not on the captured pages, and the governance add-on's exact price after its free period until January 1, 2027 depends on seat count and billing cycle — so my CFO could forecast the standard seats but not the edges.

nele.ai

The captured pages state a licensing model of "One license for all users", but show no price figures, tiers, usage limits or a per-conversation rate. My CFO could not forecast the annual cost of forty agents from what was captured.