Langdock vs nele.ai

Langdock

The terms exclude our content from training not only for Langdock but contractually for every model provider it routes to, and the Article 28 DPA is automatically concluded. Retention is ours to control — an admin-configurable chat retention period, documented deletion behaviour for files across chats, agents and knowledge bases, and deletion no later than 30 days after termination — while Azure models run with zero-data-retention abuse monitoring. Only Microsoft's abuse-monitoring terms are described, and I found no audit trail for deletions, which is what keeps this short of full accountability.

nele.ai

The privacy notice states that inputs are processed on the vendor's own servers and that AI providers are instructed not to store user inputs or use them for learning, a commitment expressly 'subject to the functions made available by the providers' — and those providers are never named. Log files are retained at most 30 days and personal data is deleted once its purpose is fulfilled, but we found no retention periods for chats or uploaded files, and the only data processing agreement evidenced is the one offered by the email provider Brevo.

Langdock

Every model provider I want named — Azure, AWS, Google Cloud, OpenAI Ireland — appears with its region, EU-only inference is the default, and processing outside the EU happens only if we actively choose a global model, with data at rest staying in EU data centres regardless. Bring-your-own-key plus managed, own-cloud and on-premises deployment are documented, and the DPA commits processing to the EU or EEA. I found no public information confirming that the EU-only switch demonstrably covers connector traffic and agent tool calls, not just chat inference.

nele.ai

A German server location is stated, with Azure in Frankfurt and Hetzner in Germany named as infrastructure providers, and user inputs are processed on the vendor's own servers. We found no public information on the models behind the assistant, their providers or the inference region, so the layer that actually generates the answers remains unattributed.

Langdock

SAML 2.0 with any compatible identity provider, SCIM, role-based access control, IP restrictions, and a governance module where admins review, approve, flag or disable agents against EU AI Act and GDPR rule templates — this is genuinely operable by IT. Retrieval mirrors the source system's permissions one-to-one, and usage analytics with CSV and API export can be disabled at workspace level. I found no public information on exportable audit logs or streaming to a SIEM, which is what holds this below the highest marks.

nele.ai

The captured pages document only that users can create a user account and that one license covers all users. We found no public information on single sign-on, provisioning, roles and groups, permission-aware retrieval, audit logs or usage reporting.

Langdock

The connector story is MCP-first: a curated directory of 79 official remote servers, any custom MCP server connectable with OAuth or API key, MCP Apps rendering interactive interfaces in a sandboxed iframe, A2A protocol support, more than 7,000 apps via Zapier, an open unified API, and agents reachable from Slack, Teams, Excel and Outlook. Integration permissions mirror the source tool one-to-one. I found no public information on sync behaviour, webhooks, or source citations on grounded answers.

nele.ai

We found no public information on connectors to file stores, wikis, mail or ticketing, on an API or open protocols such as MCP, or on how answers cite their sources. The homepage, the data-protection and security page and the knowledge-bases page we read describe none of this.

Langdock

Agents act through integration actions and MCP tools with confirmation flows, a working folder they may write to only with edit access, and workflow action nodes that run only after human confirmation, with approval configurable per run through conditions. The builder publishes versioned drafts with a test conversation beside it, and governance records a pass-or-fail compliance check on every published version with per-agent analytics, costs and history visible. I found no public information on evaluation against test sets before release or on attribution of each action to the person who deployed the agent.

nele.ai

We found no public information on agents, multi-step tasks, actions in other systems, human approval, run logs or the vendor's stated limits. Nothing in the homepage, the security page or the terms of use we captured describes them.

Langdock

Langdock GmbH of Berlin is the contracting entity, hosting runs on Microsoft Azure in Frankfurt, and every subprocessor is published with its location — the model providers Azure, AWS, Google Cloud and OpenAI Ireland all listed with EU regions, with 14 days' notice and an objection right before any change. EU inference is available, and third-country processing occurs only on our instruction, backed by standard contractual clauses in the DPA. The model providers remain US companies operating EU regions, and Sentry processes error data in the US under the Data Privacy Framework, so this is not sovereign end to end.

nele.ai

European credentials are documented: GAL Digital GmbH in Hungen as contracting entity, a stated German server location on Azure in Frankfurt and Hetzner, a named data protection officer, and a published claim of GDPR conformity with ISO 27001 certification. The subprocessor list with locations is a real strength, but it covers hosting, email, consent, payment and website services — including Stripe and Webflow in the USA, covered by the Data Privacy Framework and standard contractual clauses — and no model provider appears in it. Without the model providers named as subprocessors, an EU inference commitment and a product data processing agreement, sovereign end-to-end use cannot be established.

Langdock

Seat prices are public — €23.20 for a standard seat and €99.00 for Business Max per user per month excluding VAT, with 20% off annual billing — alongside a governance add-on at €2.80 per user per month until January 2027, workflow tiers from an included 2,500 runs per month to €449.00 per workspace per month with 40,000 runs, and per-token API rates in euros. Minimums and terms are stated, from 1,000 users for custom enterprise pricing to 5,000 seats for own-cloud or on-premises deployment. What no buyer can compute is the fair-use limit in absolute terms or any overage pricing beyond the quotas, and the enterprise tier remains a sales conversation.

nele.ai

The only pricing-related statement we found is 'One license for all users'. We found no public price figures, tiers, usage limits, add-ons or contract terms on the captured pages, so a company cannot compute an annual cost from them.