Langdock vs nele.ai

Langdock

The binding terms state that neither Langdock nor any model provider it engages may train on customer content, the DPA is auto-concluded with deletion no later than 30 days after termination, and admins can set the chat retention period, with per-object deletion behaviour documented in the help pages. Zero-data-retention is evidenced for the Azure-hosted models' abuse monitoring, but I found no public information on abuse-monitoring or zero-retention terms for the OpenAI, Google or AWS models, nor an audit trail for deletions — the published SOC 2 Type II and ISO 27001 certificates lift this above a contract-only story, but not to the top.

nele.ai

The privacy policy instructs AI providers that user inputs may not be stored or used for learning, a commitment the vendor itself hedges as subject to the functions providers make available, and no provider is named. Log files are capped at 30 days and deletion is promised when the purpose ends, but we found no public information on retention periods for chats and files or on a data processing agreement for business customers.

Langdock

Forty-plus models are reachable through one API with public per-token prices, EU-only processing is the default and non-EU inference happens only when an admin actively selects a model with global deployment, and bring-your-own-key, single-tenant, own-cloud and on-prem deployments are documented with seat minimums. The residency commitment sits in the DPA — processing generally within the EU or EEA — rather than only on a marketing page, and even global models keep data at rest in EU data centres. I found no public information listing the inference region for every individual model, or on open-weight or self-hosted models, which is what keeps this off the top step.

nele.ai

A German server location is stated and the policy says prompts are processed on the vendor's own servers rather than sent directly to AI providers, but we found no public information on which models answer, through which provider, or where inference runs. The captured pages on the vendor's AI models and providers yielded no confirmed names.

Langdock

SAML 2.0 with any compatible identity provider, SCIM, role-based access control, IP restrictions, mirrored source-tool permissions in integrations, workspace-toggleable analytics with CSV and API usage export, and a governance module that reviews, approves, flags or disables agents with automated compliance checks on every agent update — that is a real admin surface. I found no public information on exportable audit logs, DLP or content-filter policies, or streaming logs to a SIEM, which is what a regulated IT department will ask for at a thousand seats.

nele.ai

The only documented account mechanism is individual user registration; we found no public information confirming single sign-on, administrative roles, group permissions or audit logs, including on the captured pages addressing SAML 2.0 single sign-on and administrator knowledge bases.

Langdock

The MCP support is unusually deep: a directory of 79 officially operated remote servers, connection of any custom MCP server with OAuth or API-key authentication, MCP apps rendered in a sandboxed iframe with confirmation gates and loggable JSON-RPC, plus the A2A protocol, Zapier with 7,000 apps, Slack and Teams, Excel and Outlook add-ins, and a documented API priced per token. I found no public information on connector sync behaviour or frequency, on source citations for grounded answers, or on webhooks for embedding assistants in other tools.

nele.ai

We found no public information on connectors, an API, sync behaviour or source citations; the captured knowledge-base page gave no confirmed details.

Langdock

Agents run multi-step workflows of up to 2,000 steps with action nodes gated by human confirmation, approve/reject/form user-input nodes, conditional approvals so only some runs need a person, a workflow monitor for pending steps, and a builder with a test toggle and published versions with drafts in between; governance adds per-agent costs, history and pass/fail compliance checks on each new version. I found no public information on evaluation against test sets, staged rollout, or a vendor statement of what agents must not be trusted with — the terms disclaim output accuracy and bar AI-Act high-risk uses, which is not the same as an operator's warning.

nele.ai

Although the product is presented in the category of AI agents and assistants, we found no public information on what an agent can do, actions in other systems, approvals, run logs or stated limits.

Langdock

The contracting entity is Langdock GmbH of Berlin under German law with exclusive jurisdiction in Berlin, data is hosted on Microsoft Azure in Frankfurt with the EU Data Boundary enabled, and the published subprocessor list names every model provider with location — OpenAI Ireland, Google Cloud, AWS and Azure, all EU — plus Sentry in the US for error tracking under the Data Privacy Framework and contractual clauses; the DPA confines third-country transfers to explicit customer instruction. I found no public information on ownership or a parent company, and opting into global models routes inference to US data zones, so this is a well-evidenced EU setup, not sovereignty end to end.

nele.ai

Contracting entity, register court, address and hosting are German, the hosting subprocessors are named with locations (Microsoft Azure in Frankfurt, Hetzner in Gunzenhausen), and the US services Stripe and Webflow are covered by Data Privacy Framework and standard contractual clauses. But the policy itself says AI providers process user inputs and no AI provider appears in the subprocessor list, so for an AI product the subprocessor that matters most is unaccounted for.

Langdock

The public numbers are specific: €23.20 per user per month for a Standard seat and €99.00 for a seat with five times the usage, €449.00 per workspace per month for 40,000 workflow runs, €2.80 per user per month for the governance add-on after its free period, per-token API rates, a 20% annual discount, and contract terms covering pro-rata seat additions, renewal at list price and 14-day termination notice. What blocks a full annual computation: the fair-use quantities behind the seat tiers are referenced but not shown, and single-tenant, own-cloud, on-prem and enterprise pricing is contact-us from 1,000 seats up.

nele.ai

The only pricing-related statement we could confirm is "One license for all users"; we found no public price figures, tiers, usage limits or seat minimums on the captured pricing page. A company cannot compute any annual cost from this.