Skip to content

Agent-readable comparison

Langdock vs T3 Chat

Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI.

This comparison has 26 criteria with sourced findings for both products, including 26 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan.

Langdock

Agent cross-checked Support: partial

Curated multi-provider models and a task-complexity Auto mode are documented; catalogue publication is not a tested picker.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • current_models: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed.
  • auto_routing: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified.
  • Unverified multimodal_input: A model-by-model image/audio input matrix and authenticated model picker were not inspected.
  • providers Which model providers are available? [supported]: OpenAI, Anthropic, Google, Meta, Mistral and DeepSeek have named current catalogue entries. Sources: langdock:langdock:models.
  • current_models Which current models are selectable on this plan? [partial]: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. Sources: langdock:langdock:models.
  • user_choice Can users pick the model per chat? [supported]: Per-chat selection and mid-chat switching are documented. Sources: langdock:langdock:model-guide.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. Sources: langdock:langdock:model-guide.
  • multimodal_input Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. A model-by-model image/audio input matrix and authenticated model picker were not inspected.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:models, langdock:langdock:model-guide.

T3 Chat

Agent cross-checked Support: partial

Paid-account vendor replies establish manual model switching and provider routes, while the current plan-specific catalogue is unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 vendor-support context; no Free or Premier catalogue parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • providers Which model providers are available? [partial]: Pro-context vendor replies discuss Gemini, Claude and GPT routes; the FAQ separately describes OpenAI/Anthropic/Google/OpenRouter data handling. Those policy/provider names are not a complete tier-entitlement or underlying-lab catalogue. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls.
  • current_models Which current models are selectable on this plan? [unknown]: A complete current selectable-model list for Pro, Free or Premier is unverified. The FAQ claude-4.6-sonnet URL is an example, and undated support model names are not a current plan catalogue.
  • user_choice Can users pick the model per chat? [partial]: In the USD8 context discussion the vendor recommends manually switching to Gemini Flash or summarizing into a new chat with another chosen model. This supports Pro model selection as described there, but not a current all-model, effort or Free/Premier entitlement matrix. Sources: t3-chat:t3-chat:r2-pro-context-byok.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? The public T3 FAQ, Terms, Privacy/Security policies, official feedback statuses and identifiable vendor replies did not establish this detail. No authenticated account, enterprise quote or bounded fixture was used.
  • multimodal_input Which models accept images, audio or files? [unknown]: No current Pro model-by-model image/audio/file compatibility matrix was retrieved. The generic privacy upload categories do not establish a plan entitlement.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

MOD-02 Model freshness

Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models.

Langdock

Agent cross-checked Support: partial

Public dated model additions exist, but release-lag medians and guaranteed retirement notice remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Unverified release_lag_days, deprecation_notice, version_pinning: No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.
  • changelog Is there a dated public model changelog? [supported]: Changelog includes Gemini 4 Argon on 13 October, Haiku 5.5 on 8 October and GPT-6.1 Sol on 30 September 2026. Sources: langdock:langdock:changes.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.
  • version_pinning Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:changes.

T3 Chat

Agent cross-checked Support: partial

Public feature-release information is described; plan-specific pinning and version guarantees remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Public T3 Chat release information; no verified Free/Pro/Premier picker/pinning entitlement; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
  • changelog Is there a dated public model changelog? [partial]: A vendor reply says major-feature changelog lives in Discord and a website version is planned. No accessible dated model-by-model release ledger was retrieved. Sources: t3-chat:t3-chat:changelog.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
  • version_pinning Can an admin keep an older model version? [unknown]: The vendor describes pinning and a Legacy designation in the general picker discussion, without a named individual tier. Plan-specific pinning, retained model versions and admin locks remain unverified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:changelog.

MOD-03 Bring-your-own keys and provider contracts

Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract.

Langdock

Agent cross-checked Support: partial

BYOK supports customer credentials, named cloud providers and custom compatible HTTPS endpoints.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business BYOK and individually contracted Enterprise BYOK; customer provider charges separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Cloud BYOK requires separately configured completion, embedding and image routes; local/private endpoints are not implied by a cloud key.
  • own_api_keys Can the customer use its own provider API keys? [supported]: Customer keys can replace managed completion, embedding and image keys; BYOK can be selected at upgrade or enabled later by support. Sources: langdock:langdock:byok.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Guides cover customer Azure deployment settings, Google cloud and AWS Bedrock, separately from simple direct provider keys. Sources: langdock:langdock:byok-routes.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [supported]: Manual OpenAI-compatible endpoints include vLLM, LiteLLM, Ollama, TGI and LocalAI. Cloud requires public HTTPS; private/local hostnames are blocked by default. Sources: langdock:langdock:byok-routes.
  • byo_pricing Does BYO change the licence price? [partial]: Customer model usage is billed by the customer provider under BYOK. The applicable Business/Enterprise BYOK licence rate is unknown: the public Standard headline and calculator do not reconcile, and the prior hashed asset is not a stable tariff source. No BYOK seat-rate arithmetic is retained. Sources: langdock:langdock:byok, langdock:langdock:billing.
  • byo_restrictions Which features stop working with BYO? [supported]: Completion, embeddings and image models must all be configured. Deep Research needs reasoning/fast-reasoning/backbone routes; absent categories leave features non-functional. Sources: langdock:langdock:byok, langdock:langdock:research.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok, langdock:langdock:byok-routes, langdock:langdock:billing, langdock:langdock:research.

T3 Chat

Agent cross-checked Support: partial

Vendor replies support a Pro own-OpenRouter-key route, without establishing universal provider/model coverage.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 with optional customer OpenRouter key; no Free BYOK entitlement asserted; add_ons=Customer-paid OpenRouter/provider usage; model routing and verification prerequisites apply; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • own_api_keys Can the customer use its own provider API keys? [supported]: In the paid USD8 usage discussion, staff explicitly offers a customer OpenRouter key for direct request billing; the USD8 context discussion describes OpenRouter fallback. No all-provider/all-model BYOK entitlement follows. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unknown]: Can it use its own Azure OpenAI, Bedrock or Vertex deployment? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
  • byo_pricing Does BYO change the licence price? [partial]: The paid subscription and direct-provider charges are separate in the vendor discussion. A discounted BYOK-only licence and exact customer provider rates are not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
  • byo_restrictions Which features stop working with BYO? [unknown]: Current all-model BYOK compatibility is unknown: the OpenRouter-coverage request is marked Completed while the vendor says those model routes do not run through OpenRouter and rerouting requires future work. The old OpenAI GPT5 setup reply does not establish a complete current route matrix.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

MOD-04 Local and self-hosted models

Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work.

Langdock

Agent cross-checked Support: partial

Self-hosted compatible inference is a documented BYOK route with network and capability requirements.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • self_hosted_embeddings: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified.
  • feature_parity: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee.
  • vendor_hosted_open_models: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described.
  • self_hosted_chat Can chat use a customer-hosted model? [supported]: vLLM/Ollama/TGI/LocalAI routes work through OpenAI-compatible HTTPS endpoints, not localhost/private addresses on default SaaS. Sources: langdock:langdock:byok-routes.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [partial]: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. Sources: langdock:langdock:byok, langdock:langdock:byok-models.
  • feature_parity Which features fail with self-hosted models? [partial]: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. Sources: langdock:langdock:byok-models, langdock:langdock:research.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. Sources: langdock:langdock:models, langdock:langdock:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok-routes, langdock:langdock:byok, langdock:langdock:byok-models, langdock:langdock:research, langdock:langdock:models, langdock:langdock:terms.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

MOD-05 Model control and usage limits

Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use.

Langdock

Agent cross-checked Support: partial

Workspace model defaults and usage/fallback behavior are documented; per-group model/data boundaries remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • user_limits: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard.
  • Unverified model_allowlist_by_group, data_bound_models: Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.
  • model_allowlist_by_group Can admins limit models per group? [unknown]: Can admins limit models per group? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.
  • default_model Can admins set the default model? [supported]: Admins set a default across new chats and agents; users can have their own default. Sources: langdock:langdock:workspace.
  • user_limits What per-user message or token limits apply, and are they published? [partial]: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. Sources: langdock:langdock:limits, langdock:langdock:pricing.
  • limit_behaviour What happens when a limit is reached? [supported]: With no usable extra usage, Cloud falls back to GPT-6 Luna; BYOK/dedicated use configured fallback. Current responses finish, so spend can slightly overshoot. Personal API calls error rather than fall back. Sources: langdock:langdock:extra.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:limits, langdock:langdock:pricing, langdock:langdock:extra.

T3 Chat

Agent cross-checked Support: partial

Individuals have cost-based refill limits; enterprise group governance is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 cost-limit discussion and Premier account bucket reply; Free excluded from this mechanics finding; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • model_allowlist_by_group Can admins limit models per group? [unknown]: Can admins limit models per group? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
  • default_model Can admins set the default model? [unknown]: Can admins set the default model? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Pro cost-limit replies and a Premier-specific vendor support reply tie paid usage to the FAQ Base/Overage mechanics: four-hour Base refill and monthly Overage refill. No fixed token/message allowance is published;20/200 example points are illustrative, not plan capacities. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
  • limit_behaviour What happens when a limit is reached? [supported]: For these documented paid-account bucket routes, expected request cost is reserved then settled after completion; when both balances are exhausted the FAQ says to wait for refill. No Free-tier behaviour is inferred. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets, t3-chat:t3-chat:r2-paid-tier-controls.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

Company knowledge

KNOW-01 Files in chat

Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures.

Langdock

Agent cross-checked Support: partial

Format/count limits and direct previews differ from semantic search paths.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • spreadsheets: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested.
  • Unverified ocr: No shared scanned-PDF OCR or multilingual file fixture was uploaded.
  • formats Which formats are accepted? [supported]: PDF/Word/PowerPoint and text, Excel/CSV/TSV/Parquet, listed image, audio and video types are documented; Knowledge bases exclude tabular/media. Sources: langdock:langdock:files.
  • limits What size and count limits apply per file and chat? [supported]: Web 50 files/message, mobile five; agent 50 files. PDF/Office 256 MB, text 10 MB, tabular 100 MB, images 20 MB; text 8M characters and PDF 5000 pages. Sources: langdock:langdock:files, langdock:langdock:file-count.
  • ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No shared scanned-PDF OCR or multilingual file fixture was uploaded.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. Sources: langdock:langdock:files, langdock:langdock:retrieval.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [supported]: Small direct files are previewed in full where possible; agent knowledge above 20 documents uses lists/tools. Knowledge-base/synced text uses up to 50 chunks of up to 2000 characters. Sources: langdock:langdock:retrieval.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:files, langdock:langdock:file-count, langdock:langdock:retrieval.

T3 Chat

Agent cross-checked Support: partial

Paid Pro context limits and own-key fallback are documented; plan-specific upload formats/caps remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 context restrictions and optional BYOK fallback; exact upload entitlement by tier unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • formats Which formats are accepted? [unknown]: The privacy policy mentions PDF/images/text and the request is Completed, but no current individual-tier format entitlement was verified. The earlier sentence attributing browser/file-specific PDF upload bugs to a vendor reply is withdrawn because no precise reply locator was reproduced.
  • limits What size and count limits apply per file and chat? [partial]: Vendor replies distinguish context restrictions on USD8 Pro from higher-tier allowances and own-key fallback. They do not publish a complete current per-model file size/count or context-cap matrix; no32K or user-suggested MB cap is adopted. Sources: t3-chat:t3-chat:r2-pro-context-byok.
  • ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
  • spreadsheets Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-pro-context-byok.

KNOW-02 Knowledge bases and shared collections

Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope.

Langdock

Agent cross-checked Support: supported

Persistent knowledge bases and library folders have separate limits and access roles.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

  • persistent_collections Can users keep document collections across chats? [supported]: Knowledge bases persist for chat, agents, workflows and API use. Sources: langdock:langdock:knowledge.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Owner/Editor/Viewer roles; share with persons, groups or workspace, subject to workspace-sharing permission. Sources: langdock:langdock:knowledge.
  • size_limits What are the collection limits? [supported]: Cloud Knowledge bases support 1000 files, 8M characters/file. Normal folders have 100 files and 250 MB total; dedicated limits are configurable. Sources: langdock:langdock:knowledge, langdock:langdock:file-count.
  • assistant_binding Can collections be bound to an assistant? [supported]: Agent Folders attach knowledge bases/library folders/synced folders. Sources: langdock:langdock:agents.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:knowledge, langdock:langdock:file-count, langdock:langdock:agents.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-03 Enterprise connectors

Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02).

Langdock

Agent cross-checked Support: partial

Native tools, daily folder sync and customer MCP/API integrations are distinct routes.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • on_prem_sources: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Directory includes SharePoint, OneDrive, Outlook Email/Calendar and Teams. SharePoint/OneDrive also support indexed folder sync. Sources: langdock:langdock:integrations, langdock:langdock:sync.
  • google_workspace Which Google sources are connected? [supported]: Drive, Gmail, Calendar, Docs, Sheets, Slides and Meet are listed; Drive supports folder sync. Sources: langdock:langdock:integrations.
  • atlassian Confluence and Jira? [supported]: Confluence Cloud, self-hosted Confluence Data Center and Jira are in the native directory. Sources: langdock:langdock:integrations.
  • other_systems Which other business systems? [supported]: Named routes include Salesforce, ServiceNow, HubSpot, Slack, Notion, Airtable, Asana, GitHub, Azure AI Search, Kendra and Databricks; see directory for authentication and actions. Sources: langdock:langdock:integrations.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. Sources: langdock:langdock:integrations, langdock:langdock:mcp.
  • connector_provider Who builds and maintains each connector? [supported]: Langdock provides native integrations; customers build custom actions or connect official third-party MCP servers. Sources: langdock:langdock:integrations, langdock:langdock:mcp.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:sync, langdock:langdock:mcp.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-04 Permission-aware retrieval

Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation.

Langdock

Agent cross-checked Support: partial

Folder Sync checks each user source access; Purview labels add a separate, qualified control.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • source_permissions_respected: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run.
  • sensitivity_labels: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout.
  • Unverified revocation_delay: A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted.
  • source_permissions_respected Are source permissions enforced per user? [partial]: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. Sources: langdock:langdock:sync, langdock:langdock:knowledge.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: A copied content index is searched while access is checked live against the source system for synced files. Sources: langdock:langdock:sync.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins choose integrations/actions; synced folders scope imported content and labels can exclude documents. Sources: langdock:langdock:actions, langdock:langdock:labels, langdock:langdock:sync.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [partial]: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. Sources: langdock:langdock:labels.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:knowledge, langdock:langdock:labels, langdock:langdock:actions.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-05 Freshness and sync model

Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01.

Langdock

Agent cross-checked Support: partial

Folder Sync copies indexed text and refreshes daily, with live access checks and manual refresh.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • deletion_propagation: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available.
  • index_location: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped.
  • live_or_indexed Is content searched live or copied into an index? [supported]: Folder Sync downloads supported text into an index; spreadsheets remain direct-read files. Other integration actions query source APIs. Sources: langdock:langdock:sync, langdock:langdock:integrations.
  • sync_interval How often does an index refresh? [supported]: Daily updates, manual refresh and up to one hour initial sync. Sources: langdock:langdock:sync.
  • deletion_propagation How quickly does a deleted document disappear? [partial]: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. Sources: langdock:langdock:sync.
  • index_location Where is indexed content stored? [partial]: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. Sources: langdock:langdock:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:integrations, langdock:langdock:terms.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-06 Grounding and retrieval quality

Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking.

Langdock

Agent cross-checked Support: partial

Citations are documented; retrieval outcomes remain untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • citations: Agent responses cite sources by default; source-access restriction can hide click-through while still using content.
  • Unverified citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy: No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
  • citations Are answers linked to specific sources? [partial]: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. Sources: langdock:langdock:agents.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-07 Memory and personal context

Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide.

Langdock

Agent cross-checked Support: supported

Regular-chat instructions and memory have user and workspace controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

  • custom_instructions Can users set persistent instructions? [supported]: Personal instructions apply in regular chat; agent/project instructions replace them. Sources: langdock:langdock:account.
  • cross_chat_memory Does the product remember facts across chats? [supported]: Regular chats use a personal store of up to 50 memories; projects/agents do not use this memory. Sources: langdock:langdock:memory.
  • user_memory_controls Can users view, edit and delete memories? [supported]: Users inspect, edit, delete or disable memories in account settings and can update/forget through chat. Sources: langdock:langdock:memory, langdock:langdock:account.
  • admin_memory_controls Can admins turn memory off? [supported]: Memory availability requires workspace and personal enablement. Sources: langdock:langdock:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:memory, langdock:langdock:chat.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Assistants and agents

AGT-01 Custom assistants

Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here.

Langdock

Agent cross-checked Support: partial

Agents combine reusable knowledge and tools with creation/sharing controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • sharing_scope: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared.
  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Agents configure model, instructions, files, folders, integrations, subagents, skills and workflows. Sources: langdock:langdock:agents.
  • creator_permissions Can admins limit who creates them? [supported]: System/custom roles and extra permissions control agent creation/sharing. Sources: langdock:langdock:roles.
  • sharing_scope Can assistants be shared with users, groups or everyone? [partial]: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. Sources: langdock:langdock:workspace, langdock:langdock:agents.
  • catalogue Is there an internal assistant directory? [supported]: Workspace agent management has All/Unassigned/Verified views. Sources: langdock:langdock:workspace.
  • prompt_library Are shared prompt templates available? [supported]: The workspace guide documents group/workspace prompt-library sharing. Sources: langdock:langdock:workspace.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents, langdock:langdock:roles, langdock:langdock:workspace.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

AGT-02 Tools, actions and MCP

Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary.

Langdock

Agent cross-checked Support: partial

Remote MCP and custom actions have admin access controls and optional confirmations.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • tool_approval: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured.
  • builtin_tools Which tools are built in? [supported]: Search, images, file work, document editor, memory, research and company knowledge are governed tools. Sources: langdock:langdock:chat.
  • custom_actions Can admins add API actions? [supported]: Custom API integrations and shareable individual actions are documented. Sources: langdock:langdock:actions.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Streamable HTTP/SSE with OAuth CIMD/DCR/manual PKCE, API key or none; private network URLs blocked by default. Sources: langdock:langdock:mcp.
  • tool_auth Do tools act as the user or as a shared account? [supported]: Native integrations use personal OAuth or service credentials per provider; MCP supports user OAuth or API headers. Sources: langdock:langdock:integrations, langdock:langdock:mcp.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. Sources: langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:changes.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:chat, langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:integrations, langdock:langdock:changes.

T3 Chat

Agent cross-checked Support: partial

Paid Pro search is discussed by the vendor; image-tier entitlement, custom actions and MCP remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 for evidenced search use; image and MCP plan entitlement unknown; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • builtin_tools Which tools are built in? [partial]: The Pro/Premier pricing discussion explicitly describes frequent search and search-token overhead in the USD8 paid context. An OpenAI image integration has separate support evidence, but its plan entitlement is not verified and is not included as a Pro tool promise. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
  • custom_actions Can admins add API actions? [unknown]: Can admins add API actions? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
  • mcp_client Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
  • tool_auth Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls.

AGT-03 Web search and deep research

Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off.

Langdock

Agent cross-checked Support: partial

Cited search and public-web Deep Research are available; provider/region details remain incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • admin_toggle: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established.
  • Unverified search_provider: Search/crawl provider contracts and query-processing region were not established in the public tool documentation.
  • web_search Is web search available? [supported]: Chat tool generates a query and can open URLs; sources are inspectable. Sources: langdock:langdock:web.
  • admin_toggle Can admins disable it per organisation or group? [partial]: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. Sources: langdock:langdock:workspace.
  • search_provider Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unknown. Search/crawl provider contracts and query-processing region were not established in the public tool documentation.
  • deep_research Is multi-step research with a report available? [supported]: Regular chat only, public web only, cited PDF reports; standard keys allow 15 researches per rolling 30 days. BYOK needs research models. Sources: langdock:langdock:research.
  • web_citations Are web sources cited? [supported]: Search sources link to corresponding paragraphs and Deep Research has activity/source lists. Sources: langdock:langdock:web, langdock:langdock:research.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:web, langdock:langdock:workspace, langdock:langdock:research.

T3 Chat

Agent cross-checked Support: partial

Search is user-selectable, with a documented one-to-five search limit; a separate deep-research product is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 paid-search discussion; no Free parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • web_search Is web search available? [partial]: Staff’s paid USD8 discussion confirms search consumes API/query and context costs. The FAQ exposes search on/off and1..5 URL limits, but a complete current tier-specific limit/feature matrix was not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.
  • admin_toggle Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
  • search_provider Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
  • deep_research Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
  • web_citations Are web sources cited? [unknown]: Are web sources cited? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.

AGT-04 Workflows and automation

Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow.

Langdock

Agent cross-checked Support: partial

Multi-step workflows support automatic triggers and human review.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=Workflow run package; model usage separately metered; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • builder_audience: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users.
  • workflow_builder Is there a workflow or chain builder? [supported]: Workflows chain agents, integrations, logic, loops and custom code after workspace activation. Sources: langdock:langdock:workflows.
  • scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Schedule triggers are documented for workflows; the public API index also exposes recurring saved tasks. Sources: langdock:langdock:workflows.
  • event_triggers Can external events start a workflow? [supported]: Connected-app events, forms and webhooks start runs; dated composable-workflow release supports multiple triggers. Sources: langdock:langdock:workflows, langdock:langdock:changes.
  • builder_audience Is building aimed at business users, IT or developers? [partial]: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. Sources: langdock:langdock:workflows.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workflows, langdock:langdock:changes.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

AGT-05 Agentic task execution

Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof.

Langdock

Agent cross-checked Support: partial

Agents execute actions/subagents; workflow and add-in confirmation behavior is explicit.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Excel and Outlook add-ins; version=Public documentation checked 2026-10-26; plan=Business Chat & Agents/Workflows; Outlook add-in for paid plans and trials, enabled by workspace admin; add_ons=Workflow package as needed; compatible Microsoft Outlook/Exchange Online subscription; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • visible_steps: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed.
  • side_effect_confirmation: Configurable per-agent confirmations and workflow action review exist. Newly saved MCP actions default to no confirmation; Office add-ins ask before edits by default.
  • stop_control: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:agents, langdock:langdock:research, langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:agents-20261026, langdock:langdock:research-20261026, langdock:langdock:changes-20261026, langdock:langdock:hitl-20261026, langdock:langdock:mcp-20261026, langdock:langdock:excel-20261026.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

AGT-06 Programmable access

Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP.

Langdock

Agent cross-checked Support: partial

Public APIs include knowledge and agent MCP, with distinct personal/workspace governance boundaries.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-21; plan=API/Agent/Knowledge scopes; workspace activation may apply; add_ons=Metered API usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • api_governance: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits.
  • chat_api Is there an API for chat and assistants? [supported]: Public Completion and Agent APIs use scoped bearer keys. Workspace/personal key access is controlled by admins. Sources: langdock:langdock:workspace.
  • knowledge_api Can documents be loaded through an API? [supported]: Knowledge Folder API supports upload/update/delete/retrieve/search with API-key sharing roles. Sources: langdock:langdock:knowledge.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. Sources: langdock:langdock:billing, langdock:langdock:extra.
  • mcp_server Does the product expose itself to other agents over MCP? [supported]: https://api.langdock.com/mcp exposes find_agent/ask_agent/ask_custom_agent under Agent API key scope; dedicated URL differs. Sources: langdock:langdock:mcp-server.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:knowledge, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:mcp-server.

T3 Chat

Agent cross-checked Support: partial

No official programmable enterprise interface was established; subscription-backed external-agent API usage was rejected.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • chat_api Is there an API for chat and assistants? [partial]: An official feedback request asks to apply subscription quota to external coding agents/API; staff closes it because the economics do not work. The FAQ URL launches a browser chat and is not a documented chat API. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.
  • knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
  • api_governance Do audit, budgets and model rules apply to API use? [unknown]: Do audit, budgets and model rules apply to API use? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.

Daily work

WORK-01 Clients and access points

Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website.

Langdock

Agent cross-checked Support: partial

Web, desktop and mobile clients are documented, with IT deployment guidance.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Windows/macOS desktop, Langdock iOS/Android; version=Public documentation checked 2026-10-21; plan=Business or contracted Enterprise workspace clients; the same subscription/approved models apply; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=Windows, macOS, iOS, Android.

Limitations

  • Native-client and SSO parity beyond the documented file limit was not tested. The source is installation guidance, not proof of a paid Enterprise-only client entitlement.
  • web Is a full web client available? [supported]: The core platform is a browser workspace. Sources: langdock:langdock:terms.
  • desktop_apps Windows and macOS apps? [supported]: Official Windows/macOS downloads use the same workspace and approved models as web. This is documented availability, not a hands-on parity test. Sources: langdock:langdock:desktop-product.
  • mobile_apps iOS and Android apps with SSO? [partial]: The vendor publishes iOS/Android clients and official store links. Mobile-specific SSO and managed-access compatibility were not independently tested. Sources: langdock:langdock:mobile-rev2, langdock:langdock:mobile-product.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. A general browser extension and exhaustive mobile/SSO/Intune parity matrix were not established.
  • managed_deployment Can IT deploy and configure clients through MDM? [partial]: Windows machine-wide MSIX/Intune and deployment kits are documented. macOS PKG/DMG works with Jamf, Kandji and Intune. These are client installation methods; separate mobile MAM/dedicated entitlements are not established by this finding. Sources: langdock:langdock:desktop-rev2.
  • client_feature_gaps Which features are missing on mobile? [partial]: Mobile permits five files per message versus 50 on web; other parity gaps were not tested. Sources: langdock:langdock:file-count.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:desktop-product, langdock:langdock:mobile-rev2, langdock:langdock:mobile-product, langdock:langdock:desktop-rev2, langdock:langdock:file-count.

T3 Chat

Agent cross-checked Support: partial

A browser client and iOS TestFlight beta are documented; desktop, Android release and managed clients remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application, T3 Chat iOS TestFlight beta; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Browser account plan; iOS TestFlight beta; enterprise SSO unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=iOS.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • web Is a full web client available? [supported]: T3 Chat is delivered as a browser service; the FAQ documents launching new conversations through public URLs. Sources: t3-chat:t3-chat:faq-url.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
  • mobile_apps iOS and Android apps with SSO? [partial]: The vendor’s September10,2026 announcement releases iOS via TestFlight explicitly as beta; Android beta is coming soon. Neither corporate SSO nor a production app-store release was verified. Sources: t3-chat:t3-chat:mobile.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-url, t3-chat:t3-chat:mobile.

WORK-02 Office suite and Teams integration

Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02.

Langdock

Agent cross-checked Support: partial

Excel and Outlook add-ins and a Teams bot are documented; broad Office-suite coverage is not inferred.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock Excel and Outlook add-ins, Langdock Teams bot; version=Public documentation checked 2026-10-26; plan=Business or Enterprise workspace; Outlook available on paid plans/trials, Excel/Teams require workspace-admin enablement; add_ons=Compatible Microsoft licences not priced; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • word_excel_powerpoint: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established.
  • licence_prerequisites: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced.
  • Unverified google_workspace_apps: Google in-editor apps were not established; Google content integrations are recorded separately.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [partial]: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. Sources: langdock:langdock:excel.
  • outlook Does it work inside Outlook? [supported]: Outlook reads connected mailbox/calendar and edits drafts; sending requires a requested action and confirmation. Exchange Online is required. Sources: langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace.
  • teams Is there a Teams app or bot? [supported]: Admin-installed Teams bot supports private chat and collaborative channel mentions. Sources: langdock:langdock:teams, langdock:langdock:teams-20261026.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Google in-editor apps were not established; Google content integrations are recorded separately. Rechecked 2026-10-26 in Outlook Add-in, Excel Add-in, How to use the Teams Bot. The Teams Markdown guide was retrieved with HTTP 200; Google in-editor app coverage remains undocumented in these sources.
  • licence_prerequisites Which licences or consents are needed? [partial]: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:teams, langdock:langdock:outlook-marketplace, langdock:langdock:teams-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:teams, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:excel-20261026, langdock:langdock:teams-20261026.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-03 Translation and writing

Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results.

Langdock

Agent cross-checked Support: partial

DeepL integration offers document translation and glossaries; end-to-end layout quality is untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • document_translation: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial.
  • glossaries: DeepL integration lists glossary management; full enterprise glossary rollout was not tested.
  • Unverified formality_and_variants: Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified.
  • document_translation Can whole documents be translated with formatting kept? [partial]: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. Sources: langdock:langdock:integrations.
  • translation_engine Which engine translates? [supported]: The dedicated DeepL integration uses the customer DeepL API key; ordinary chat rewriting uses the chosen model. Sources: langdock:langdock:integrations.
  • glossaries Are company glossaries supported? [partial]: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. Sources: langdock:langdock:integrations.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified.
  • writing_tools Are dedicated rewrite and proofreading tools available? [supported]: DeepL integration includes writing polish; Document Editor supports selected-text and whole-document AI edits. Sources: langdock:langdock:integrations, langdock:langdock:editor.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:editor.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-04 Image generation and editing

Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images.

Langdock

Agent cross-checked Support: partial

Image generation and model-specific editing are documented with workspace controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • image_generation: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst.
  • image_editing: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified.
  • usage_terms: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable.
  • image_generation Can users generate images, with which models? [partial]: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. Sources: langdock:langdock:images, langdock:langdock:changes.
  • image_editing Can users edit uploaded images? [partial]: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. Sources: langdock:langdock:changes, langdock:langdock:byok-models.
  • admin_control Can admins restrict image generation? [supported]: Workspace admins can disable image generation and manage available models. Sources: langdock:langdock:workspace.
  • usage_terms What usage rights apply to output? [partial]: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. Sources: langdock:langdock:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:images, langdock:langdock:changes, langdock:langdock:byok-models, langdock:langdock:workspace, langdock:langdock:terms.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-05 Voice and meetings

Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed.

Langdock

Agent cross-checked Support: partial

Audio/meeting-source integrations are documented; live voice and Swiss German remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • read_aloud: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control.
  • meeting_summaries: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run.
  • Unverified dictation, voice_conversation, swiss_german_speech: Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.
  • dictation Can users dictate prompts? [unknown]: Can users dictate prompts? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.
  • read_aloud Can answers be read aloud? [partial]: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. Sources: langdock:langdock:integrations.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.
  • meeting_summaries Are meetings transcribed and summarised? [partial]: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. Sources: langdock:langdock:integrations.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-06 Data analysis and document output

Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable.

Langdock

Agent cross-checked Support: partial

File analysis, charts and editable document generation are documented; execution-location detail is incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • data_analysis: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified.
  • canvas_editing: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files.
  • data_analysis Can it analyse spreadsheets with executed code? [partial]: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. Sources: langdock:langdock:analysis.
  • charts Can it produce charts? [supported]: Charts and downloadable chart images are supported in the guide. Sources: langdock:langdock:analysis.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Analysis lists Excel/CSV/Word/PDF/JSON; changelog and agent file templates also describe PowerPoint. Sources: langdock:langdock:analysis, langdock:langdock:changes.
  • canvas_editing Is there a document or canvas editor for iterating on output? [partial]: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. Sources: langdock:langdock:editor.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:analysis, langdock:langdock:changes, langdock:langdock:editor.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-07 Sharing and team spaces

Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to.

Langdock

Agent cross-checked Support: partial

Shared projects expose chats/files, and Teams channels support group interaction.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Teams bot; version=Public documentation checked 2026-10-21; plan=Business/Enterprise workspace sharing; Teams bot requires workspace-admin setup and Microsoft tenant installation; add_ons=Microsoft Teams access; bot installed and permitted by tenant admin; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Unverified share_permission_boundary: No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers.
  • share_chats Can chats be shared inside the organisation? [supported]: Workspace chat-link sharing is managed under account shared chats. Sources: langdock:langdock:account.
  • team_spaces Are shared projects or workspaces available? [supported]: Projects shared with users/groups include all current and future project chats, files and instructions; cannot share a project to the whole workspace. Sources: langdock:langdock:projects.
  • group_chat Can several people chat together with the AI? [supported]: Teams channel threads allow several people to participate with @Langdock. Sources: langdock:langdock:teams.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:projects, langdock:langdock:teams.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

WORK-08 Interface languages and accessibility

Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements.

Langdock

Agent cross-checked Support: partial

Five interface languages are documented; quality and accessibility have not been audited.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.
  • ui_languages Which UI languages are offered? [supported]: English, German, Spanish, French and Italian are listed in Account Preferences. Sources: langdock:langdock:account.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Administration and governance

ADM-01 Single sign-on and authentication

Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible.

Langdock

Agent cross-checked Support: partial

Business includes SAML SSO and verified domains; MFA relies on the identity provider.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • mfa: No standalone Langdock MFA; SAML identity provider enforces MFA.
  • Unverified conditional_access: OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: SAML 2.0 with Entra ID, Google Workspace and Okta; account docs also name Google/Microsoft SSO. Sources: langdock:langdock:saml, langdock:langdock:account.
  • sso_plan Which plan includes SSO? [supported]: Business up to 1000 users includes SSO, SCIM and SAML. Sources: langdock:langdock:billing.
  • mfa Can MFA be enforced? [partial]: No standalone Langdock MFA; SAML identity provider enforces MFA. Sources: langdock:langdock:saml.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established.
  • domain_capture Can the company claim its email domain? [supported]: Join by domain and verified email domains are prerequisites for SAML; SAML remains required on those verified domains. Sources: langdock:langdock:saml.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:saml, langdock:langdock:account, langdock:langdock:billing.

T3 Chat

Agent cross-checked Support: partial

The security policy asserts MFA support without documenting enterprise SAML/OIDC administration.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • sso_protocols Which SSO protocols and identity providers work? [partial]: Security policy refers to OAuth provider accounts and standard authentication without naming enterprise SAML/OIDC protocols or supported corporate IdPs. Sources: t3-chat:t3-chat:security.
  • sso_plan Which plan includes SSO? [unknown]: Which plan includes SSO? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
  • mfa Can MFA be enforced? [partial]: The vendor asserts MFA support and recommends two-factor protection at the OAuth provider. Enforceable organization-wide MFA settings were not established. Sources: t3-chat:t3-chat:security.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
  • domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:security.

ADM-02 User provisioning and lifecycle

Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content.

Langdock

Agent cross-checked Support: partial

SCIM synchronizes users/groups and preserves functioning ownerless agents.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • deprovisioning: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh.
  • seat_assignment: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription.
  • Unverified jit_provisioning: Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified.
  • scim Is SCIM provisioning supported? [supported]: SCIM 2.0 via Entra, with prior SAML and verified domains. Sources: langdock:langdock:scim.
  • group_sync Are identity-provider groups synced? [supported]: Entra SCIM group sync is documented and can be disabled; default group roles are separately configurable. Sources: langdock:langdock:scim-entra, langdock:langdock:workspace.
  • jit_provisioning Are users created at first login? [unknown]: Are users created at first login? Unknown. Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. Sources: langdock:langdock:scim-entra, langdock:langdock:leaver, langdock:langdock:sync.
  • seat_assignment Can admins assign and reclaim seats? [partial]: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. Sources: langdock:langdock:workspace.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:scim, langdock:langdock:scim-entra, langdock:langdock:workspace, langdock:langdock:leaver, langdock:langdock:sync.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

ADM-03 Roles, groups and feature permissions

Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group.

Langdock

Agent cross-checked Support: partial

System/custom roles and delegated groups govern product and action permissions.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • feature_toggles: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established.
  • Unverified multi_entity: Subsidiary/contract-level isolation beyond group and workspace boundaries was not established.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Member, Editor, Admin, up to five custom roles and extra permissions; group admins are separate from workspace admins. Sources: langdock:langdock:roles.
  • groups Can permissions be set per group? [supported]: Groups can be SCIM-synced, admin-created or user-created if allowed; group rights and resources are distinct from system roles. Sources: langdock:langdock:workspace.
  • feature_toggles Which features can be switched on or off per group? [partial]: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. Sources: langdock:langdock:roles, langdock:langdock:actions, langdock:langdock:workspace.
  • multi_entity Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? Unknown. Subsidiary/contract-level isolation beyond group and workspace boundaries was not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:roles, langdock:langdock:workspace, langdock:langdock:actions.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

ADM-04 Usage and adoption analytics

Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring.

Langdock

Agent cross-checked Support: supported

Analytics and exports cover adoption and consumption with user-detail controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

  • adoption_dashboard Is there an adoption dashboard? [supported]: Active users, message trends, agent/group counts and leaderboards are documented. Sources: langdock:langdock:workspace.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Products, models, users, groups, API keys, agents, workflows, projects and add-ins have dashboard/export breakdowns. Sources: langdock:langdock:workspace, langdock:langdock:exports.
  • export Can usage data be exported? [supported]: CSV and Usage Export API, up to 12 months, one million rows per export and 15-minute generation limit. Sources: langdock:langdock:exports.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [supported]: User-level data toggle omits listed identifying fields from CSV; whole analytics can be disabled via support. Sources: langdock:langdock:exports, langdock:langdock:workspace.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:exports.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

ADM-05 Spend controls and cost allocation

Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts.

Langdock

Agent cross-checked Support: partial

Chat/BYOK, workspace API and workflows have separate spend controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • budget_enforcement: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation.
  • chargeback: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:byok, langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits, langdock:langdock:exports.

T3 Chat

Agent cross-checked Support: partial

Individual consumption indicators exist; organization budgets and chargeback remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 and Premier account consumption mechanics; no organization/admin budget offer asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: The paid Pro discussion and Premier support reply describe per-account cost/bucket consumption. The FAQ describes separate balance displays; exact placement and model-cost indicators are not a customer organization reporting entitlement. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
  • budgets Can budgets be set per user or group? [unknown]: Can budgets be set per user or group? No customer organization/user-group budget assignment or cost-centre export was retrieved.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: For the documented paid-account bucket routes, exhausting both balances requires waiting for refill. This does not establish configurable user/group currency budgets, alerts or downgrade policies. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets.
  • chargeback Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No customer organization/user-group budget assignment or cost-centre export was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

ADM-06 Audit logs and compliance export

Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model.

Langdock

Agent cross-checked Support: partial

Enterprise dedicated deployment documents separate administrative-event and conversation-content export APIs. Cloud content export requires workspace enablement and is outside this dedicated finding.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Audit events, usage rows and conversation-content exports are distinct API functions. The dedicated-deployment behavior is not universal Business Cloud availability.
  • admin_events Are admin and security events logged? [partial]: API logs workspace/model/role/skill/action/workflow changes and failed logins with actor/IP/diff; immutable storage guarantees were not verified. Sources: langdock:langdock:audit.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: Dedicated deployments serve the Compliance API unless disabled for that deployment. A key with the Compliance API scope is required. Conversation message content and tool inputs/outputs are included only when include_message_content=true and include_action_results=true are both set. On Cloud the scope is hidden and requests return 404 until workspace enablement; Business Cloud entitlement is not inferred. Sources: langdock:langdock:compliance-rev2-20261026.
  • siem_export Can logs stream to a SIEM or be exported? [supported]: Cursor-paginated event API is documented for SIEM ingestion, under AUDIT_LOG_API scope. Sources: langdock:langdock:audit.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. Native legal hold/eDiscovery and audit integrity guarantees were not established. Rechecked 2026-10-26 in Audit Logs API Overview, Export tool parameters and outputs.
  • log_retention How long are logs kept? [supported]: Administrative audit events have documented90-day retention. Conversation data follows the deployment workspace retention settings. A separate SaaS workflow pricing retention period is not asserted for this dedicated deployment. Sources: langdock:langdock:audit, langdock:langdock:workspace, langdock:langdock:pricing.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:audit, langdock:langdock:compliance-rev2, langdock:langdock:workspace, langdock:langdock:pricing, langdock:langdock:compliance-rev2-20261026, langdock:langdock:audit-20261026, langdock:langdock:workspace-20261026, langdock:langdock:pricing-20261026.

T3 Chat

Agent cross-checked Support: partial

The privacy policy describes vendor telemetry, not a customer compliance logging service.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • admin_events Are admin and security events logged? [unknown]: Are admin and security events logged? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: The privacy policy collects prompts/uploads and Terms reserve review/removal for violations. A configurable customer prompt/answer compliance archive was not established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
  • siem_export Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
  • log_retention How long are logs kept? [unknown]: How long are logs kept? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

ADM-07 Data loss prevention and personal data

Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome.

Langdock

Agent cross-checked Support: partial

Purview source filtering is documented; generic prompt/file PII redaction remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • dlp_integration: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions.
  • filter_location: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector.
  • Unverified pii_detection, pii_action, custom_patterns: The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
  • pii_detection Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
  • pii_action Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
  • custom_patterns Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
  • dlp_integration Does it integrate with an existing DLP product? [partial]: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. Sources: langdock:langdock:labels.
  • filter_location Where does filtering run? [partial]: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. Sources: langdock:langdock:labels.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:labels.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

ADM-08 AI policy and guardrails

Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow.

Langdock

Agent cross-checked Support: partial

Instructions, disclaimers and agent compliance checks exist; prompt-level topic enforcement remains incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • org_instructions: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field.
  • usage_notice: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established.
  • content_filters: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable.
  • violation_reporting: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. Sources: langdock:langdock:workspace.
  • usage_notice Can users be required to accept a usage policy? [partial]: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. Sources: langdock:langdock:workspace.
  • content_filters Are content filters configurable? [partial]: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. Sources: langdock:langdock:gov.
  • violation_reporting Are policy hits visible to admins? [partial]: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. Sources: langdock:langdock:gov.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:gov.

T3 Chat

Agent cross-checked Support: partial

Acceptable-use terms apply, while organization policy controls remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • org_instructions Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
  • usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
  • content_filters Are content filters configurable? [partial]: Terms prohibit categories of unlawful/harmful content and permit vendor review/removal or suspension. Customer configurable content filters are not established. Sources: t3-chat:t3-chat:terms.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Data protection and sovereignty

DATA-01 Hosting location and data residency

Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions.

Langdock

Agent cross-checked Support: partial

Default Azure Frankfurt/EU storage and provider-specific inference are contractually distinguished.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • backups_logs_region: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed.
  • swiss_hosting: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency.
  • support_access_region: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified.
  • storage_region Where are chats, files and indexes stored? [supported]: Terms Appendix 1 places files, prompts, outputs and embeddings in selected EU Azure data centres; Frankfurt named. Sources: langdock:langdock:terms.
  • inference_region Where do model calls run, per provider? [supported]: Azure, OpenAI, Google, AWS Bedrock and Mistral have described EU routes. Opt-in Global Azure/Google/AWS/OpenAI routes can infer worldwide, including US; default model enablement is EU only. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace.
  • backups_logs_region Where are backups, logs and telemetry? [partial]: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. Sources: langdock:langdock:dpa.
  • support_access_region From where can vendor staff access data? [partial]: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. Sources: langdock:langdock:account.
  • swiss_hosting Is Swiss hosting available? [partial]: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. Sources: langdock:langdock:byok-models.
  • residency_plan Which plan or option provides residency? [supported]: Standard multi-tenant uses EU Azure; global model activation is a controller instruction under DPA section 8. Sources: langdock:langdock:security, langdock:langdock:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace, langdock:langdock:byok-models, langdock:langdock:account, langdock:langdock:security.

T3 Chat

Agent cross-checked Support: partial

The privacy policy places the service under US/international processing; no EU/Swiss end-to-end option was established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • storage_region Where are chats, files and indexes stored? [partial]: The policy says services are provided in the United States and information is processed there or in other countries; Azure, AWS and Vercel are named. Component-specific chat/file/index storage regions are not enumerated. Sources: t3-chat:t3-chat:privacy.
  • inference_region Where do model calls run, per provider? [partial]: The policy names OpenAI, Google, Anthropic and OpenRouter processing, but no provider-by-provider region, EU-only switch or customer region guarantee is supplied. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.
  • backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
  • support_access_region From where can vendor staff access data? [unknown]: From where can vendor staff access data? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
  • residency_plan Which plan or option provides residency? [unknown]: Which plan or option provides residency? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.

DATA-02 Deployment options

Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment.

Langdock

Agent cross-checked Support: partial

Deployment minimums differ from Enterprise subscription entry.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Standard SaaS; Enterprise 1000+; managed dedicated 2000+; own cloud/on-premise 5000+; add_ons=Deployment and operations quoted; deployment_mode=not specified; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • customer_cloud: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific.
  • on_premise: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here.
  • mode_feature_gaps: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found.
  • Unverified air_gapped: Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: Standard multi-tenant SaaS is hosted on Microsoft Azure within EU. Sources: langdock:langdock:security.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [supported]: Langdock-managed single-tenant SaaS from 2000+ seats. Sources: langdock:langdock:security.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. Sources: langdock:langdock:security.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. Sources: langdock:langdock:security.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. Sources: langdock:langdock:account, langdock:langdock:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:account, langdock:langdock:chat.

T3 Chat

Agent cross-checked Support: partial

A hosted web service is offered; tenant architecture and alternative deployment contracts remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • multi_tenant_saas Is a shared SaaS offered? [partial]: The public web service accepts individual accounts and processes content with hosting/model providers. Its exact multitenant architecture and boundaries are not documented in the retrieved public material. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
  • mode_feature_gaps Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.

DATA-03 Training use and provider retention

Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so.

Langdock

Agent cross-checked Support: supported

Microsoft Azure model routes use the contract-described no-training and Modified Abuse Monitoring configuration. Other providers are outside this finding.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise managed Microsoft Azure model routes only; BYOK and Fable/other-provider routes excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default; explicitly selected global Azure models may infer outside EU; os=not specified.

Limitations

  • Fable5/5.1 and direct/OpenAI image/file exceptions are outside this Azure-only scope; no platform-wide ZDR claim is made.
  • vendor_training Does the vendor train on customer content? [supported]: Terms section9 prohibits Langdock use of customer data for model development, training or improvement. Sources: langdock:langdock:terms-rev2.
  • provider_training Do model providers train on it under this product's contracts? [supported]: Appendix1 Microsoft Azure obligations exclude sharing customer prompts/files/embeddings with model developers and using them to train or improve models. Sources: langdock:langdock:terms-rev2.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [supported]: For the scoped Microsoft Azure model route, Langdock states Modified Abuse Monitoring disables provider storage of prompts/outputs for abuse monitoring. Platform conversation storage is separate. Sources: langdock:langdock:terms-rev2.
  • zero_retention Is zero data retention available, and on which plan? [supported]: The Azure route has the Modified Abuse Monitoring zero-retention configuration described in Appendix1. This does not establish ZDR for arbitrary customer keys or other providers. Sources: langdock:langdock:terms-rev2.
  • human_review Can provider staff review content? [supported]: Appendix1 states Azure human abuse review of the scoped prompts/outputs is disabled by Modified Abuse Monitoring. Sources: langdock:langdock:terms-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms-rev2.

T3 Chat

Agent cross-checked Support: partial

No vendor training is asserted, with provider exceptions and customer-key responsibility explicitly retained.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • vendor_training Does the vendor train on customer content? [supported]: FAQ says T3 does not train its own models and the privacy policy says personal information is not used to train AI models. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.
  • provider_training Do model providers train on it under this product's contracts? [supported]: The FAQ says OpenAI/Anthropic defaults are not opted into training, Google paid models disable training and OpenRouter training routes are disabled. Some new models may require training and are labeled; BYOK customers manage their own provider settings. Sources: t3-chat:t3-chat:faq-training.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
  • zero_retention Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
  • human_review Can provider staff review content? [unknown]: Can provider staff review content? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.

DATA-04 Retention and deletion

Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation.

Langdock

Agent cross-checked Support: partial

Admins control chat retention; file cleanup depends on all remaining references.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • default_retention: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention.
  • user_deletion: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files.
  • default_retention What is retained and for how long by default? [partial]: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. Sources: langdock:langdock:retention, langdock:langdock:pricing.
  • admin_retention Can admins set retention periods? [supported]: Chat inactivity retention options are seven days, one/three/twelve months or forever, with daily irreversible deletion. Sources: langdock:langdock:workspace.
  • user_deletion Can users delete their chats and files permanently? [partial]: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. Sources: langdock:langdock:retention.
  • contract_end_deletion What is deleted at contract end, and when? [supported]: DPA section 11 requires deletion within 30 days of termination subject to legal retention, confirmation on request and export access until deletion. Sources: langdock:langdock:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:retention, langdock:langdock:pricing, langdock:langdock:workspace, langdock:langdock:dpa.

T3 Chat

Agent cross-checked Support: partial

Termination export responsibilities are contractual; plan-specific temporary-chat behaviour and retention remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual T3 Chat service Terms; temporary-chat Free/Pro/Premier entitlement not established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.
  • default_retention What is retained and for how long by default? [unknown]: The generic URL FAQ distinguishes temporary and persisted threads but does not map that feature to a named individual tier or specify server/provider/file/backup retention. No plan-specific temporary-chat retention claim is made.
  • admin_retention Can admins set retention periods? [unknown]: Can admins set retention periods? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
  • user_deletion Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
  • contract_end_deletion What is deleted at contract end, and when? [partial]: Terms put responsibility on users to export before termination and endeavor to provide a reasonable retrieval opportunity only for vendor-convenience termination; deletion timing and certificate are unspecified. Sources: t3-chat:t3-chat:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

DATA-05 Sub-processors and foreign-law exposure

Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment.

Langdock

Agent cross-checked Support: partial

DPA publishes seven default subprocessors and conditional Global routes with transfer mechanisms.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • parent_jurisdiction: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established.
  • government_access_policy: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found.
  • subprocessor_list Is a dated sub-processor list published? [supported]: DPA 2.1 Appendix 2 embeds the current named list; trust-centre subprocessor page needs client rendering and did not return text. Sources: langdock:langdock:dpa.
  • subprocessor_countries Which countries do sub-processors operate in? [supported]: Default entities: Microsoft Ireland, AWS EMEA Luxembourg, Google Cloud EMEA Ireland, OpenAI Ireland, Mistral France, Sentry US and Cloudflare US; default processing column is EU. Global opt-ins include worldwide/US inference and Azure EU storage. Sources: langdock:langdock:dpa.
  • change_notification Are customers notified of sub-processor changes? [supported]: At least 14 days before new/replaced subprocessor via public register and email only if subscribed; objection within 14 days of publication. Sources: langdock:langdock:dpa.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. Sources: langdock:langdock:terms.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA lists EU-US/Swiss-US DPF, UK extension and EU/UK SCCs with Swiss addenda per provider; Global OpenAI lists EU/UK SCCs. Sources: langdock:langdock:dpa.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. Sources: langdock:langdock:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:dpa, langdock:langdock:terms.

T3 Chat

Agent cross-checked Support: partial

Named providers and a US vendor address are public, without a complete processor-country or transfer contract matrix.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • subprocessor_list Is a dated sub-processor list published? [partial]: The May31,2025 privacy policy names Azure, AWS, Vercel, OpenAI, Google, Anthropic and OpenRouter, explicitly non-exhaustively. This is not established as a complete Article28 subprocessor schedule. Sources: t3-chat:t3-chat:privacy.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
  • change_notification Are customers notified of sub-processor changes? [partial]: Privacy policy says material changes are posted with an updated effective date. A processor-addition notice period and objection right are not specified. Sources: t3-chat:t3-chat:privacy.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The policy and Terms identify T3 Tools Inc with a San Francisco address and US/California legal context. A separate parent entity, incorporation jurisdiction and ownership were not independently established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
  • government_access_policy Is there a published government-access or transparency policy? [partial]: The policy allows disclosures for subpoenas, warrants and legal investigations. No separate transparency report or detailed challenge/notification policy was retrieved. Sources: t3-chat:t3-chat:privacy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

DATA-06 Contracts and regulatory coverage

Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict.

Langdock

Agent cross-checked Support: partial

DPA automatically forms part of German-law terms; Swiss and sector materials need qualification.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • dpa: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised.
  • revdsg_gdpr: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established.
  • ai_act_materials: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier.
  • sector_materials: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained.
  • dpa Is a DPA available, and is it negotiable? [partial]: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. Sources: langdock:langdock:terms, langdock:langdock:dpa.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. Sources: langdock:langdock:dpa.
  • governing_law Which law and court govern the contract? [supported]: German law, Berlin exclusive jurisdiction; German language version binds over English translation. Sources: langdock:langdock:terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. Sources: langdock:langdock:pricing, langdock:langdock:gov.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. Sources: langdock:langdock:legal.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:pricing, langdock:langdock:gov, langdock:langdock:legal.

T3 Chat

Agent cross-checked Support: partial

Public consumer/service terms use California law; an enterprise GDPR/Swiss DPA remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • dpa Is a DPA available, and is it negotiable? [unknown]: Is a DPA available, and is it negotiable? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [unknown]: Does the DPA cover revDSG and GDPR? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
  • governing_law Which law and court govern the contract? [supported]: Terms section19 uses California law and individual JAMS arbitration in Santa Clara County, with small-claims/injunction exceptions and state/federal Santa Clara courts where arbitration does not apply. Sources: t3-chat:t3-chat:terms.
  • ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
  • sector_materials Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

DATA-07 Certifications and attestations

Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product.

Langdock

Agent cross-checked Support: partial

ISO 27001 and SOC 2 Type II are vendor claims pending certificate/report verification.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • iso_27001: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved.
  • soc2: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved.
  • report_access: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method.
  • pentest: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved.
  • Unverified c5, other_certifications: No C5, other product certificate, issuer-register verification or gated report was established.
  • iso_27001 ISO 27001 with scope and validity? [partial]: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. Sources: langdock:langdock:security.
  • soc2 SOC 2 type, period and covered service? [partial]: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. Sources: langdock:langdock:security.
  • c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No C5, other product certificate, issuer-register verification or gated report was established.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No C5, other product certificate, issuer-register verification or gated report was established.
  • report_access How can customers obtain reports? [partial]: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. Sources: langdock:langdock:legal.
  • pentest Are independent penetration test summaries available? [partial]: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. Sources: langdock:langdock:security.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:legal.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

DATA-08 Encryption and key control

Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN).

Langdock

Agent cross-checked Support: partial

Encryption and network restrictions are documented; customer key custody is not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • private_networking: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established.
  • Unverified customer_managed_keys, tenant_isolation: Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.
  • encryption_at_rest Is data encrypted at rest? [supported]: Vendor states AES-256 storage and TLS 1.2+ transport. Sources: langdock:langdock:security.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.
  • private_networking Is private connectivity or IP restriction available? [partial]: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. Sources: langdock:langdock:ip.
  • tenant_isolation How are customers separated in shared SaaS? [unknown]: How are customers separated in shared SaaS? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:ip.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

DATA-09 Professional secrecy

Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment.

Langdock

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

T3 Chat

Agent cross-checked Support: partial

Public policies describe vendor/provider content processing, but professional-secrecy contracts and a business plan remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual account service; no business/professional-secrecy offer verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US/international policy; no DE/CH-specific arrangement verified; os=not specified.

Limitations

  • No-training statements and personal account terms are not a professional-secrecy undertaking.
  • No legal suitability or compliance conclusion.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public DPA or signed/signon §203 StGB/Art321 StGB professional-secrecy undertaking covering T3 staff was retrieved from the Terms, privacy/security policies or targeted first-party searches.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy names hosting/model services but does not establish a dedicated professional-secrecy undertaking binding them. Its existence and flow-down are unknown.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: A team/business offer itself remains unverified; no professional-secrecy-specific tier, dedicated package or paid add-on was established.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Privacy policy sends input to selected OpenAI/Google/Anthropic/OpenRouter services; Terms reserve vendor review/removal of content upon apparent violations. This establishes processing/review possibilities, not an exhaustive plaintext staff/provider access matrix or protected-profession arrangement. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public consumer/service Terms and privacy/security pages were reviewed, with targeted §203/Art321/professional-secrecy searches. No specific template, protected-profession data-flow statement or professional-body guidance was retrieved; no private agreement was requested.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

Commercials and vendor

VEN-01 Pricing model and list prices

Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment.

Langdock

Agent cross-checked Support: partial

Business uses seats with included managed-chat usage; workflow/API and other add-ons are separate. An applicable Standard/BYOK licence tariff is not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents and optional modules; Enterprise quoted at1000+; applicable Standard/BYOK tariff unknown; add_ons=Workflows, Governance, API/Extra Usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Inconsistent price representations are retained as a named price gap, not combined into a synthetic tariff.
  • pricing_unit What is the pricing unit? [supported]: Seat/month platform, per-workspace workflow packages, metered API/workflow AI/extra usage, optional per-seat Governance. Sources: langdock:langdock:pricing-rev2.
  • list_prices What are list prices per plan, with date and currency? [unknown]: Unknown applicable Standard/BYOK seat tariff. The public Business headline is EUR25 while the annual price breakdown starts at EUR23.20; billing docs refer to the same pricing page without reconciling them. Enterprise1000+ is quote-only. Prior hashed-calculator rates are excluded.
  • included_usage What usage is included? [partial]: Standard includes managed chat/agent usage under five-hour and weekly windows; Max has 5x. Precise numerical included cost budgets are not public. Starter includes 2500 workflow runs/month but no workflow model tokens. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits.
  • add_ons Which features cost extra? [partial]: Workflow Starter includes2500runs/month with AI tokens billed separately. The public add-on page lists40k/100k packages and Governance free until2027-01-01, then separately priced per base-plan seat. The applicable binding package/billing-period amounts are not established here. Sources: langdock:langdock:pricing-rev2.
  • overage What do usage beyond limits and premium models cost? [supported]: Extra usage is charged at API rates. Model page lists GPT-5 Mini EUR 0.22 input/1.78 output per million; workflow and API spend use separate caps. Sources: langdock:langdock:extra, langdock:langdock:models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits, langdock:langdock:extra, langdock:langdock:models.

T3 Chat

Agent cross-checked Support: partial

Individual subscription prices are supported by vendor replies; quotas are cost-based and checkout/organization details are incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Staff pricing replies are first-party but undated; current checkout amounts and tax/plan availability were not observed.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai.

VEN-02 Scenario cost

Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts.

Langdock

Agent cross-checked Support: partial

All requested200/1000/5000-user totals are unknown because an applicable Business Standard tariff or Enterprise quote is not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Standard up to1000 users; Enterprise1000+; all applicable scenario licence totals unknown; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60/30/10 users at100/400/1500messages monthly,3000input+600output tokens/message. Only separately billed usage uses this token mix.
  • ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Unknown base/variable components prevent totals; no silent conversion.
  • cost_200 Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for200users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
  • cost_1000 Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for1000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
  • cost_5000 Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for5000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
  • variable_share Which part depends on usage? [partial]: Managed Business chat includes model usage subject to usage limits. ExtraUsage,workflow/API,Governance and customer-provider BYOK bills are separate. Missing applicable tariff/allowance components remain unknown; no proxy substitutes for vendor-billed usage. Sources: langdock:langdock:billing, langdock:langdock:extra.
  • unknown_parts Which costs could not be priced? [partial]: Business Standard/BYOK applicable seat rate, Enterprise licence/deployment quote, workload-preserving overage and required modules/services are unknown. This prevents a verifiable EUR/CHF total. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:ecb-fx.

T3 Chat

Agent cross-checked Support: partial

Multiplying individual list prices yields conditional licence floors, not a verified organization quote or usage-complete TCO.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Conditional independent Pro/Premier account multiplication; no organization plan verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Known price floor + unknown components; no complete year-one TCO, seat commitment or sufficient-usage guarantee.
  • cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months,list prices,exVAT,no negotiated discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330,each3000 input+600 output tokens incl retrieval. Vendor subscription usage remains subject to cost/refill limits; no fixed default/recommended model or complete tariff is published, so coverage and variable extra cost stay unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; divideUSD by1.1215 then multiplyEUR by0.9237. For200 separate accounts: Pro from USD19,200/EUR17,119.93/CHF15,813.68 + unknown; Premier reference USD120,000/EUR106,999.55/CHF98,835.49 + unknown. Bulk purchase and business-governance fit unverified. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
  • cost_1000 Year-one cost at 1,000 users? [partial]: Same assumptions,1000 separate accounts: Pro from USD96,000/EUR85,599.64/CHF79,068.39 + unknown; Premier reference USD600,000/EUR534,997.77/CHF494,177.44 + unknown. Not a1000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
  • cost_5000 Year-one cost at 5,000 users? [partial]: Same assumptions,5000 separate accounts: Pro from USD480,000/EUR427,998.22/CHF395,341.95 + unknown; Premier reference USD3,000,000/EUR2,674,988.85/CHF2,470,887.20 + unknown. Not a5000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
  • variable_share Which part depends on usage? [partial]: Included usage consumes a cost meter with no complete published tariff/default model. For an optional direct-provider BYOK comparison only, the shared gpt-6-luna effort-none Standard proxy is USD0.10 input/USD0.50 output per1M and USD2.376/user/year at the shared mix, excluding cache/tools/embeddings/regional uplift. This exact model/route is not verified selectable in T3 and is not added to the subscription floor as though it were a vendor tariff. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model.
  • unknown_parts Which costs could not be priced? [supported]: Unpriced: enterprise/bulk entitlement, organization features, exact current checkout prices, model availability and complete token/search/file tariff, whether the shared workload fits refill quotas, direct-provider/OpenRouter route charges, regional processing and support/implementation. No assumed wholesale discount or model-cost subsidy. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:byok-router.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:byok-router.

VEN-03 Evaluation access

Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval.

Langdock

Agent cross-checked Support: partial

A seven-day self-serve business trial is advertised without a card.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • free_tier: Terms describe a time-limited trial that ends automatically; permanent business free access is not established.
  • trial_scope: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run.
  • sales_gate: Base trial is self-serve; enterprise deployment and custom terms require an offer.
  • free_tier Is there a free tier for business use? [partial]: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. Sources: langdock:langdock:terms.
  • self_serve_trial Is a self-serve business trial available? [supported]: Seven days, no card, EUR 5 model credit and team invitations. Sources: langdock:langdock:pricing.
  • trial_scope Do trials include SSO, connectors and admin features? [partial]: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. Sources: langdock:langdock:pricing.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; enterprise deployment and custom terms require an offer. Sources: langdock:langdock:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:pricing, langdock:langdock:billing.

T3 Chat

Agent cross-checked Support: partial

Free usage is in the Terms; a business-specific trial and enterprise evaluation path remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • free_tier Is there a free tier for business use? [partial]: Terms say services are free up to unspecified usage limits and paid resources may be required. Organizational acceptance is allowed, but no free business admin entitlement is established. Sources: t3-chat:t3-chat:terms.
  • self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
  • trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: A public browser service and free-limited offer are documented; business-specific meaningful evaluation and any sales gate cannot be determined without an established business offer. Sources: t3-chat:t3-chat:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

VEN-04 Contract terms and pricing transparency

Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint.

Langdock

Agent cross-checked Support: partial

Monthly/annual contract defaults and EUR invoices are public; some pricing representations conflict.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • minimum_commitment: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ.
  • local_invoicing: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established.
  • transparency_class: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ.
  • minimum_commitment What seat or spend minimum applies? [partial]: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. Sources: langdock:langdock:pricing, langdock:langdock:security.
  • contract_length What contract lengths are offered? [supported]: Monthly or annual; annual offers 20% reduction on Standard tiers. Sources: langdock:langdock:billing.
  • cancellation How can the contract be cancelled or reduced? [supported]: Terms specify seven-day notice before monthly end, fourteen days before annual/multiyear end; automatic monthly/12-month renewals; notices by text/email or platform. Sources: langdock:langdock:terms.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. Sources: langdock:langdock:terms.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. Sources: langdock:langdock:pricing, langdock:langdock:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing, langdock:langdock:security, langdock:langdock:billing, langdock:langdock:terms.

T3 Chat

Agent cross-checked Support: partial

Individual monthly upgrades/downgrades are documented; business minimums and European invoicing remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • minimum_commitment What seat or spend minimum applies? [partial]: The public evidence concerns individual accounts and monthly prices, not a minimum team-seat/spend commitment. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
  • contract_length What contract lengths are offered? [supported]: Vendor replies confirm monthly Premier pricing and billing periods; no signed annual or business-term offer was retrieved. Sources: t3-chat:t3-chat:premier.
  • cancellation How can the contract be cancelled or reduced? [supported]: Terms permit account cancellation at any time without refunds. Staff says upgrades take effect immediately and downgrades at the billing-period end. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? No team minimum, European contracting entity or CHF/EUR invoice entitlement was retrieved.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: some individual prices are confirmed in undated staff replies, complete final checkout requires billing information, quotas are not a public token tariff, and a business offer remains unverified. Sources: t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage.

VEN-05 Source licence

Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse.

Langdock

Agent cross-checked Support: partial

Commercial platform rights are proprietary and time-limited.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • licence_type: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated.
  • branding_restrictions: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP.
  • Unverified enterprise_features_closed: A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established.
  • licence_type Which licence applies to each component? [partial]: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. Sources: langdock:langdock:terms.
  • branding_restrictions Do licence terms restrict branding or user counts? [partial]: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. Sources: langdock:langdock:terms.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms.

T3 Chat

Agent cross-checked Support: partial

The hosted service is proprietary; clone hackathons and T3 Code are separate products.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • licence_type Which licence applies to each component? [supported]: Terms grant a personal nonassignable service licence and prohibit copying, modification, reverse engineering and source extraction, subject to third-party software rights. Sources: t3-chat:t3-chat:terms.
  • branding_restrictions Do licence terms restrict branding or user counts? [supported]: Terms reserve vendor trademarks and prohibit sublicensing/renting/providing service access to others; each account is personal and cannot be shared. Sources: t3-chat:t3-chat:terms.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? No supported self-host licence, open-source core/enterprise split or enterprise edition licence was retrieved. Public third-party clones are not licensed distributions of the hosted product.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

VEN-06 Data export and exit

Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable.

Langdock

Agent cross-checked Support: partial

Enterprise dedicated resource/configuration and conversation-content APIs document exports. A complete source/index/ACL workspace exit bundle has not been established.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • Configuration/file APIs are separate from conversation export. Dedicated Compliance API availability does not establish a Business Cloud entitlement.
  • chat_export Can admins export all chats? [partial]: The dedicated-deployment Compliance API documents paginated conversation/message exports. include_message_content=true adds messages; both it and include_action_results=true add tool arguments and outputs. A scoped key is required. Cloud workspaces need separate enablement and no Business Cloud entitlement is inferred. Sources: langdock:langdock:compliance-rev2-20261026.
  • assistant_export Can assistants and prompts be exported in a reusable format? [partial]: Agent API Get/Create migration exports configuration; attachments/skills must be handled separately and some fields/ownership do not transfer. Sources: langdock:langdock:migration.
  • knowledge_export Can knowledge bases and their sources be exported? [partial]: Knowledge Folder API can retrieve/list files; a complete original-source/index/ACL export bundle was not demonstrated. Sources: langdock:langdock:knowledge, langdock:langdock:knowledge-20261026.
  • export_format Are formats documented and machine-readable? [partial]: Agent and Compliance API JSON plus usage CSV/JSON are documented; this is not a one-click complete workspace export. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:exports, langdock:langdock:exports-20261026.
  • post_termination_window How long can data be retrieved after termination? [supported]: DPA permits exports during contract and until deletion, which occurs no later than30 days after termination subject to legal retention. Sources: langdock:langdock:dpa.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:knowledge, langdock:langdock:exports, langdock:langdock:dpa, langdock:langdock:compliance-rev2-20261026, langdock:langdock:migration-20261026, langdock:langdock:knowledge-20261026, langdock:langdock:exports-20261026, langdock:langdock:dpa-20261026.

T3 Chat

Agent cross-checked Support: partial

Terms require pre-termination export, but a documented organizational export package was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • chat_export Can admins export all chats? [unknown]: Can admins export all chats? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
  • export_format Are formats documented and machine-readable? [unknown]: Are formats documented and machine-readable? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
  • post_termination_window How long can data be retrieved after termination? [partial]: Users must export before termination. If the vendor terminates for convenience it will endeavor to allow a reasonable retrieval opportunity; no fixed post-termination window is guaranteed. Sources: t3-chat:t3-chat:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

VEN-07 Support and service levels

Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score.

Langdock

Agent cross-checked Support: partial

Berlin vendor support, public status history and a 99% monthly availability term are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • support_channels: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels.
  • uptime_sla: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published.
  • Unverified support_languages: Contractual DE/FR/IT support languages, full hours/timezone and dedicated response/credit schedules were not established.
  • support_channels Which support channels are available on each plan? [partial]: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. Sources: langdock:langdock:billing, langdock:langdock:playbook.
  • support_languages Is support available in German, French or Italian? [partial]: The imprint says users and authorities can contact support@langdock.com in German and English. It does not specify contractual French or Italian support, hours or response times. Sources: langdock:langdock:imprint-20261026.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [supported]: Langdock GmbH contracts from Berlin, Germany. Sources: langdock:langdock:terms.
  • uptime_sla Is there an uptime SLA with credits? [partial]: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. Sources: langdock:langdock:terms.
  • status_page Is there a public status page with history? [supported]: Public status separates app/API/Workflow/Integration history. Sources: langdock:langdock:status.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:billing, langdock:langdock:playbook, langdock:langdock:terms, langdock:langdock:status, langdock:langdock:imprint-20261026, langdock:langdock:terms-20261026, langdock:langdock:status-20261026.

T3 Chat

Agent cross-checked Support: partial

Email support and official feedback are public, without a retrieved SLA or regional-language contract.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

  • Documented findings only; unestablished atomic questions remain explicit gaps.
  • support_channels Which support channels are available on each plan? [supported]: The FAQ lists a support email and official feature/bug board; plan-specific response targets are not published there. Sources: t3-chat:t3-chat:faq-support.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: The vendor publishes a San Francisco contact address. A DACH/Swiss entity, partner or support team was not established. Sources: t3-chat:t3-chat:privacy.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
  • status_page Is there a public status page with history? [unknown]: Is there a public status page with history? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-support, t3-chat:t3-chat:privacy.

VEN-08 Onboarding, training and adoption

Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings.

Langdock

Agent cross-checked Support: partial

Rollout support starts at 250 licences; public learning material and champion guidance are available.

Availability: generally-available · Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations

  • onboarding_service: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract.
  • user_training: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified.
  • service_cost: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found.
  • onboarding_service Is guided onboarding included? [partial]: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. Sources: langdock:langdock:playbook.
  • user_training Is end-user training offered, in which languages? [partial]: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. Sources: langdock:langdock:training.
  • use_case_library Are role-based use cases and templates provided? [supported]: Playbook recommends role-specific prompts/agents and gives structured use-case discovery material. Sources: langdock:langdock:playbook.
  • adoption_programme Is there a champion or adoption programme? [supported]: Playbook includes department champions, follow-ups, hackathons and AI challenges. Sources: langdock:langdock:playbook.
  • service_cost Which services cost extra? [partial]: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. Sources: langdock:langdock:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:playbook, langdock:langdock:training, langdock:langdock:billing.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Sources

  1. AI Models | Langdock langdock:langdock:models

    Public model table lists current text models and EUR metered prices.

    Provider tables · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  2. Model Guide langdock:langdock:model-guide

    Users select models or Auto routing; reasoning levels vary by model.

    Selecting a Model, Auto and Thinking · documented · Source date not stated · Retrieved 2026-10-21

  3. T3 Chat FAQ t3-chat:t3-chat:faq-training

    The vendor says it does not train models, configures OpenAI/Anthropic/paid Google/OpenRouter no-training where possible, labels exceptions and makes BYOK customers responsible for settings.

    Do you use my data for training? · documented · Source date not stated · Retrieved 2026-10-21

  4. Usage model change t3-chat:t3-chat:billing-change

    Vendor replies confirm current cost-based usage and that an USD8 subscription can still use expensive models within cost limits.

    Mark Florkowski Team replies · documented · Source date not stated · Retrieved 2026-10-21

  5. Pro/Premier vendor replies t3-chat:t3-chat:r2-paid-tier-controls

    The vendor discusses USD8 Pro usage/search costs, optional OpenRouter keys and Premier USD50/month; this does not establish Free parity or a complete model matrix.

    Mark Florkowski Team: cost explanation, OpenRouter direct billing, USD50 Premier and plan changes · documented · Source date not stated · Retrieved 2026-10-21

  6. Context and own-key controls t3-chat:t3-chat:r2-pro-context-byok

    Vendor replies document context restrictions on the USD8 tier and optional own-key fallback without publishing a complete current model/file matrix.

    Mark Florkowski Team replies on USD8 limits, higher tier, model switching and OpenRouter fallback · documented · Source date not stated · Retrieved 2026-10-21

  7. Product Changelog | Langdock langdock:langdock:changes

    Dated releases document model additions, desktop apps and per-agent confirmations.

    13 October 2026 model release; 15/10 September feature releases · documented · Source date not stated · Retrieved 2026-10-21

  8. Changelog of new features t3-chat:t3-chat:changelog

    A vendor reply says major-feature changelog is in Discord and a website version is intended; the website request remains Planned.

    Planned status and Mark Florkowski Team reply · documented · Source date not stated · Retrieved 2026-10-21

  9. https://docs.langdock.com/en/admin/billing/pricing.md langdock:langdock:billing

    Business covers up to 1000 users, BYOK separates model costs, workflows/API are metered and Enterprise is quoted.

    Products, volume tiers, Enterprise and API · documented · Source date not stated · Retrieved 2026-10-21

  10. https://docs.langdock.com/en/admin/byok/byok.md langdock:langdock:byok

    BYOK replaces completion, embedding and image routes; missing model categories break relevant features.

    Options, requirements, setup and usage export · documented · Source date not stated · Retrieved 2026-10-21

  11. Setup Guides langdock:langdock:byok-routes

    Named BYOK routes include cloud providers, Vercel Gateway and self-hosted OpenAI-compatible HTTPS endpoints.

    Provider setup tabs and OpenAI-compatible endpoints · documented · Source date not stated · Retrieved 2026-10-21

  12. Deep Research langdock:langdock:research

    Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

    Model configuration, limitations and usage · documented · Source date not stated · Retrieved 2026-10-21

  13. Terms of Use | Langdock langdock:langdock:terms

    Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

    Sections 6/7/9/12/15/16/19 and Appendix 1 · documented · Source date not stated · Retrieved 2026-10-21

  14. How to add your own models langdock:langdock:byok-models

    Admins configure completion, image and embedding models, deployments, capability flags and USD accounting rates.

    Custom model setup and deployment configuration · documented · Source date not stated · Retrieved 2026-10-21

  15. Pricing Plans | Langdock langdock:langdock:pricing

    Business headline prices, annual discounts, workflow packages and Governance promotion are public.

    Chat & Agents, price breakdown, add-ons and API · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  16. Workspace Settings langdock:langdock:workspace

    Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

    Product Settings, Models, Analytics and Customizations · documented · Source date not stated · Retrieved 2026-10-21

  17. Usage Limits langdock:langdock:limits

    Five-hour and weekly usage windows trigger extra usage or a fallback; spam protection caps 250 messages per three hours.

    Usage windows and exhaustion · documented · Source date not stated · Retrieved 2026-10-21

  18. Extra Usage langdock:langdock:extra

    Extra usage has workspace/plan/user caps and fallback behavior with possible final-response overshoot.

    Enabling extra usage, spend limits and API exceptions · documented · Source date not stated · Retrieved 2026-10-21

  19. T3 Chat FAQ t3-chat:t3-chat:faq-usage

    Base refills every four hours and Overage monthly; usage reserves then settles request cost and blocks until refill when both are depleted. Example20/200 points are illustrative, not published quota sizes.

    How does the usage meter work? · documented · Source date not stated · Retrieved 2026-10-21

  20. Premier usage-limit support t3-chat:t3-chat:r2-premier-buckets

    The identifiable vendor reply specifically applies the FAQ bucket mechanics to a Premier account.

    Mark Florkowski Team reply explaining exhausted monthly overage and four-hour bucket · documented · Source date not stated · Retrieved 2026-10-21

  21. Which file types does Langdock support? langdock:langdock:files

    Supported files have different type-specific size limits and processing restrictions.

    Format/size tables and processing limits · documented · Source date not stated · Retrieved 2026-10-21

  22. What are the file limits in the chat and in agents? langdock:langdock:file-count

    Web message uploads allow 50 files, mobile five; agent knowledge and knowledge bases have separate limits.

    Chat and agent attachment limits · documented · Source date not stated · Retrieved 2026-10-21

  23. Knowledge Basics langdock:langdock:retrieval

    Direct file previews differ from semantic search over 2000-character chunks, returning up to 50 passages.

    Direct context and embedding search · documented · Source date not stated · Retrieved 2026-10-21

  24. Knowledge bases langdock:langdock:knowledge

    Persistent shareable knowledge bases accept up to 1000 text documents, search chunks and attach to agents.

    Creation, sharing, limits and agent use · documented · Source date not stated · Retrieved 2026-10-21

  25. Agent Configuration langdock:langdock:agents

    Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

    Agent configuration, knowledge and source restriction · documented · Source date not stated · Retrieved 2026-10-21

  26. Folder Sync langdock:langdock:sync

    Daily folder sync supports SharePoint, OneDrive, Drive and Confluence, with real-time user access checks.

    Setup, permission checks, sync behavior and owner removal · documented · Source date not stated · Retrieved 2026-10-21

  27. Integration Directory langdock:langdock:integrations

    The native directory lists Microsoft, Google, Atlassian, CRM, BI, vector search, DeepL and audio integrations.

    Native integration directory · documented · Source date not stated · Retrieved 2026-10-21

  28. Model Context Protocol (MCP) langdock:langdock:mcp

    MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

    Transports, authentication and tool confirmation · documented · Source date not stated · Retrieved 2026-10-21

  29. Sensitivity Label Policy langdock:langdock:labels

    A request-enabled Purview label policy filters supported integrations, with documented actions and upload exceptions.

    Availability, enforcement, exceptions and unsupported areas · documented · Source date not stated · Retrieved 2026-10-21

  30. Manage Action Access langdock:langdock:actions

    Admins share integrations and actions with users/groups/API keys; native core actions cannot be disabled.

    Access settings and native-action exception · documented · Source date not stated · Retrieved 2026-10-21

  31. Basic Chat functionalities langdock:langdock:chat

    Chat supports model selection and governed tools; memory, deep research and agent tool conditions differ.

    Model selector and tool availability · documented · Source date not stated · Retrieved 2026-10-21

  32. Account Settings langdock:langdock:account

    Account settings include five UI languages, personal controls and temporary 72-hour Support sharing.

    Preferences, shared chats, custom instructions and memory · documented · Source date not stated · Retrieved 2026-10-21

  33. Memory langdock:langdock:memory

    Memory works in regular chats only, with a 50-memory cap and view/edit/delete controls.

    Availability, management and limits · documented · Source date not stated · Retrieved 2026-10-21

  34. Roles and extra permissions langdock:langdock:roles

    System roles, up to five custom roles and delegated group permissions are configurable.

    System roles, custom roles and group permissions · documented · Source date not stated · Retrieved 2026-10-21

  35. Web Search langdock:langdock:web

    Web search returns inspectable citations and has a separate open-URL tool.

    Search behavior and source inspection · documented · Source date not stated · Retrieved 2026-10-21

  36. T3 Chat FAQ t3-chat:t3-chat:faq-url

    A new-chat URL selects a model, reasoning effort, search on/off, one to five searches, a profile and temporary/persisted storage mode.

    Custom search URLs and query parameter table · documented · Source date not stated · Retrieved 2026-10-21

  37. Introduction to Workflows langdock:langdock:workflows

    Workflows chain agents, integrations and logic with form, schedule and event triggers after admin activation.

    Introduction and activation · documented · Source date not stated · Retrieved 2026-10-21

  38. Human in the Loop langdock:langdock:hitl

    Workflow runs can pause for editor approval or per-action confirmation.

    Approval and action confirmation · documented · Source date not stated · Retrieved 2026-10-21

  39. Excel Add-in langdock:langdock:excel

    The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

    Install, workbook operations and edit permissions · documented · Source date not stated · Retrieved 2026-10-21

  40. Outlook Add-in langdock:langdock:outlook-rev2

    The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

    Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  41. Langdock for Outlook, by Langdock GmbH langdock:langdock:outlook-marketplace

    Vendor listing offers the add-in to every paid Langdock plan and trials, with draft review before sending.

    Overview and eligibility sentence · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  42. Outlook Add-in langdock:langdock:outlook-rev2-20261026

    The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

    Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-26

  43. Pricing Plans | Langdock langdock:langdock:pricing-20261026

    Business headline prices, annual discounts, workflow packages and Governance promotion are public.

    Chat & Agents, price breakdown, add-ons and API · vendor-claimed · Source date not stated · Retrieved 2026-10-26

  44. Product Changelog | Langdock langdock:langdock:changes-20261026

    Dated releases document model additions, desktop apps and per-agent confirmations.

    13 October 2026 model release; 15/10 September feature releases · documented · Source date not stated · Retrieved 2026-10-26

  45. Outlook Add-in setup langdock:langdock:outlook-admin-20261026

    Admins set Outlook add-in access to Nobody, Everyone or Specific members and groups; Outlook Email and Calendar integrations have separate access/scopes.

    Availability and access settings · documented · Source date not stated · Retrieved 2026-10-26

  46. Agent Configuration langdock:langdock:agents-20261026

    Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

    Agent configuration, knowledge and source restriction · documented · Source date not stated · Retrieved 2026-10-26

  47. Deep Research langdock:langdock:research-20261026

    Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

    Model configuration, limitations and usage · documented · Source date not stated · Retrieved 2026-10-26

  48. Human in the Loop langdock:langdock:hitl-20261026

    Workflow runs can pause for editor approval or per-action confirmation.

    Approval and action confirmation · documented · Source date not stated · Retrieved 2026-10-26

  49. Model Context Protocol (MCP) langdock:langdock:mcp-20261026

    MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

    Transports, authentication and tool confirmation · documented · Source date not stated · Retrieved 2026-10-26

  50. Excel Add-in langdock:langdock:excel-20261026

    The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

    Install, workbook operations and edit permissions · documented · Source date not stated · Retrieved 2026-10-26

  51. Langdock Agent MCP Server langdock:langdock:mcp-server

    A public MCP endpoint exposes workspace agents under Agent API scope.

    Endpoint, authentication and tools · documented · Source date not stated · Retrieved 2026-10-21

  52. Subscription-backed API request t3-chat:t3-chat:api-request

    Staff rejects the economics of applying a T3 Chat subscription to external coding-agent/API usage; an official general chat API is not established.

    Closed status and Mark Florkowski Team reply · documented · Source date not stated · Retrieved 2026-10-21

  53. Enterprise Guide for Langdock Desktop langdock:langdock:desktop-rev2

    Managed desktop rollout supports machine-wide Windows packages and signed/notarized macOS installers; these installation instructions do not change subscription entitlements.

    Windows machine-wide MSIX/Intune; macOS PKG/DMG/Jamf/Kandji; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  54. Mobile App langdock:langdock:mobile-rev2

    HTTP200 Markdown introduction links official Apple App Store and Google Play mobile clients.

    Download routes · documented · Source date not stated · Retrieved 2026-10-21

  55. Langdock Desktop langdock:langdock:desktop-product

    Windows/macOS desktop clients use the same workspace and approved models as web.

    Downloads and Q&A · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  56. Langdock Mobile langdock:langdock:mobile-product

    Vendor mobile page offers iOS/Android clients using the workspace-approved models.

    App Store/Google Play links and Q&A · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  57. Mobile App t3-chat:t3-chat:mobile

    The vendor released an iOS TestFlight beta on September10,2026 and says Android beta is coming soon.

    Mark Florkowski, Team, pinned September10,2026 announcement · documented · Source date 2026-09-10 · Retrieved 2026-10-21

  58. How to use the Teams Bot langdock:langdock:teams

    Teams has personal bot chats and channel threads with team participation.

    Private chats, channels and admin install · documented · Source date not stated · Retrieved 2026-10-21

  59. How to use the Teams Bot langdock:langdock:teams-20261026

    The public Markdown guide was retrieved with HTTP 200. A workspace admin installs the Teams app, which supports private bot chat and channel threads using @Langdock; it is separate from the web chat history.

    Installation note; Two Ways to Use the Teams Bot; Private Chat; Using Langdock in Channels; Limitations · documented · Source date not stated · Retrieved 2026-10-26

  60. Document Editor langdock:langdock:editor

    Document Editor replaces Canvas and exports Markdown, Word and PDF; imported Word/PDF cannot be edited directly there.

    Editor, AI edits, export and limitations · documented · Source date not stated · Retrieved 2026-10-21

  61. Image Generation langdock:langdock:images

    Chat invokes configured image-generation models with a user model selector.

    Generating images and model choice · documented · Source date not stated · Retrieved 2026-10-21

  62. Using Langdock for Data Analysis langdock:langdock:analysis

    Tabular analysis produces charts and downloadable spreadsheet and document formats.

    Analysis procedure and outputs · documented · Source date not stated · Retrieved 2026-10-21

  63. Projects langdock:langdock:projects

    Shared projects expose all project chats/files to members and can be shared with users/groups, not the whole workspace.

    Project sharing and permissions · documented · Source date not stated · Retrieved 2026-10-21

  64. https://docs.langdock.com/en/admin/security/saml/saml.md langdock:langdock:saml

    SAML 2.0 requires a verified domain; MFA comes from the IdP rather than standalone Langdock MFA.

    Checklist, supported IdPs, external authentication and MFA · documented · Source date not stated · Retrieved 2026-10-21

  65. T3 Chat security policy t3-chat:t3-chat:security

    The vendor asserts TLS, MFA support, secure sessions/access control and regular audits; no independent report or enterprise enforcement configuration is supplied.

    Data protection, authentication and disclosure program · vendor-claimed · Source date 2025-02-14 · Retrieved 2026-10-21

  66. https://docs.langdock.com/en/admin/security/scim/scim.md langdock:langdock:scim

    SCIM 2.0 supports Entra provisioning after SAML setup and domain verification.

    Overview and prerequisites · documented · Source date not stated · Retrieved 2026-10-21

  67. https://docs.langdock.com/en/admin/security/scim/entra.md langdock:langdock:scim-entra

    Entra target actions control provisioning/deactivation and group synchronization.

    Target Object Actions and optional group synchronization · documented · Source date not stated · Retrieved 2026-10-21

  68. Unassign Agents langdock:langdock:leaver

    Agents whose owner is deactivated keep functioning but cannot be edited until reassigned.

    Unassigned agents and reassignment · documented · Source date not stated · Retrieved 2026-10-21

  69. Usage Exports langdock:langdock:exports

    Usage CSV exports span users, agents, keys, projects, models and workflows, with user-detail privacy controls.

    Export data types, limits and user-level data · documented · Source date not stated · Retrieved 2026-10-21

  70. Usage and spend limits langdock:langdock:byok-limits

    BYOK cost limits depend on configured prices and exclude backbone, workflows and workspace API usage.

    Scope, unpriced models and spend limits · documented · Source date not stated · Retrieved 2026-10-21

  71. Workflow limits langdock:langdock:workflow-limits

    Workflow AI use has a separate workspace EUR limit and per-workflow USD limits that block new runs.

    Spend limits and execution step cap · documented · Source date not stated · Retrieved 2026-10-21

  72. Audit Logs API Overview langdock:langdock:audit

    Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

    Event schema, retention and prerequisites · documented · Source date not stated · Retrieved 2026-10-21

  73. Export tool parameters and outputs langdock:langdock:compliance-rev2

    Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags.

    Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-21

  74. Export tool parameters and outputs langdock:langdock:compliance-rev2-20261026

    Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags.

    Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 · documented · Source date not stated · Retrieved 2026-10-26

  75. Audit Logs API Overview langdock:langdock:audit-20261026

    Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

    Event schema, retention and prerequisites · documented · Source date not stated · Retrieved 2026-10-26

  76. Workspace Settings langdock:langdock:workspace-20261026

    Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

    Product Settings, Models, Analytics and Customizations · documented · Source date not stated · Retrieved 2026-10-26

  77. T3 Chat privacy policy t3-chat:t3-chat:privacy

    The policy covers user uploads, named hosting/model providers, no AI training, US/international processing and general disclosure practices.

    Sections1-7 and11 · documented · Source date 2025-05-31 · Retrieved 2026-10-21

  78. T3 Chat Terms of Service t3-chat:t3-chat:terms

    T3 Tools Inc permits organizational acceptance but each account is personal; proprietary restrictions, cancellation/export responsibilities and California dispute terms apply.

    Sections1-6,9,19 and21 · documented · Source date 2025-11-15 · Retrieved 2026-10-21

  79. Compliance Rules langdock:langdock:gov

    Custom agent compliance checks produce pass/fail and severity results with per-rule analytics.

    Rule operation, failures and analytics · documented · Source date not stated · Retrieved 2026-10-21

  80. security langdock:langdock:security

    Default Azure EU SaaS, managed dedicated from 2000 and customer-cloud/on-premise from 5000 seats are advertised.

    Deployment, security, BYOK and certifications · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  81. Data Processing Agreement | Langdock langdock:langdock:dpa

    DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

    Sections 7-12 and Appendices 1/2 · documented · Source date not stated · Retrieved 2026-10-21

  82. Terms of Use | Langdock langdock:langdock:terms-rev2

    Microsoft Azure routes use Modified Abuse Monitoring, disabling provider prompt/output retention and human abuse review. Other provider/model routes require separate assessment.

    Section9 and Appendix1 Microsoft Azure service terms · documented · Source date not stated · Retrieved 2026-10-21

  83. How long are files saved in Langdock? langdock:langdock:retention

    Deleted chats are immediately unavailable and unreferenced files are cleaned overnight; shared file references survive.

    Retention by object type · documented · Source date not stated · Retrieved 2026-10-21

  84. https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md langdock:langdock:legal

    DPA applies automatically and a Professional Secrecy Addendum and certificates are linked from the Trust Center.

    Legal and compliance links · documented · Source date not stated · Retrieved 2026-10-21

  85. IP Restrictions langdock:langdock:ip

    CIDR allowlists immediately block unauthorized network access when enabled.

    Prerequisites and enforcement · documented · Source date not stated · Retrieved 2026-10-21

  86. Pricing Plans | Langdock langdock:langdock:pricing-rev2

    The page maps Business to up to1000 users and Enterprise to1000+; the Standard headline and breakdown disagree, so no applicable Standard/BYOK tariff is established here.

    Business/Enterprise cards; price breakdown; product add-ons · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  87. Overage bucket refill option t3-chat:t3-chat:overage

    The vendor says top-up refill has not been offered since the new billing model.

    Mark Florkowski Team reply · documented · Source date not stated · Retrieved 2026-10-21

  88. Pro and Premier pricing discussion t3-chat:t3-chat:premier

    The vendor confirms Premier USD50/month plus tax, immediate upgrades and end-period downgrades, and customer OpenRouter keys for direct usage billing.

    Mark Florkowski Team replies on price, OpenRouter, upgrades and downgrades · documented · Source date not stated · Retrieved 2026-10-21

  89. Paid price visibility t3-chat:t3-chat:price-visibility

    Staff says billing information is needed for final tax-inclusive pricing; no checkout was completed.

    Mark Florkowski Team replies · documented · Source date not stated · Retrieved 2026-10-21

  90. OpenAI BYOK t3-chat:t3-chat:byok-openai

    Staff confirms GPT5 BYOK and recommends fallback priority plus a verified OpenAI organization or removing the key; this is historical model-specific setup, not a complete current model list.

    Mark Florkowski Team reply · documented · Source date not stated · Retrieved 2026-10-21

  91. ECB historical euro reference rates, 20 October 2026 langdock:langdock:ecb-fx

    ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206.

    Cube time=2026-10-20, USD and CHF currency entries · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  92. OpenRouter model coverage t3-chat:t3-chat:byok-router

    The request is marked Completed but the staff reply says those routes do not use OpenRouter and universal rerouting requires future changes.

    Completed label versus Mark Florkowski Team reply · documented · Source date not stated · Retrieved 2026-10-21

  93. ECB reference exchange rates t3-chat:t3-chat:fx

    EUR1 equals USD1.1215 and CHF0.9237.

    Cube time2026-10-20 · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  94. OpenAI API pricing t3-chat:t3-chat:openai-price

    The shared direct-provider proxy uses USD0.10 input/USD0.50 output per million tokens; T3 availability of this exact route is unverified.

    Standard short-context gpt-6-luna row · documented · Source date not stated · Retrieved 2026-10-21

  95. GPT-6 Luna documentation t3-chat:t3-chat:openai-model

    The shared direct-provider proxy uses lowest effort none; this is not a verified T3 default or model-menu entry.

    Reasoning effort options · documented · Source date not stated · Retrieved 2026-10-21

  96. Agent Migration Guide langdock:langdock:migration

    Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

    Prerequisites, exported settings and field mapping · documented · Source date not stated · Retrieved 2026-10-21

  97. Data Processing Agreement | Langdock langdock:langdock:dpa-20261026

    DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

    Sections 7-12 and Appendices 1/2 · documented · Source date not stated · Retrieved 2026-10-26

  98. Agent Migration Guide langdock:langdock:migration-20261026

    Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

    Prerequisites, exported settings and field mapping · documented · Source date not stated · Retrieved 2026-10-26

  99. Knowledge bases langdock:langdock:knowledge-20261026

    The public Markdown guide was retrieved with HTTP 200. The Knowledge Folder API can upload, update, delete, retrieve and search files; Viewer supports retrieval, while writes need Editor. This does not establish a complete index/ACL workspace export bundle.

    Create a Knowledge base and add documents, API upload; Share search access; Convert a Knowledge base to a folder · documented · Source date not stated · Retrieved 2026-10-26

  100. Usage Exports langdock:langdock:exports-20261026

    The public Markdown guide was retrieved with HTTP 200. Workspace administrators can export usage analytics as CSV or through the Usage Export API, with up to 12 months of history and JSON-valued mapping fields. Usage analytics are distinct from a complete chat/knowledge export.

    Accessing Usage Exports; Export Limits; Export Data Structure; Usage Exports; Data Retention · documented · Source date not stated · Retrieved 2026-10-26

  101. Rollout Playbook langdock:langdock:playbook

    Dedicated rollout support/workshops start at 250 licences and include a champion approach.

    Programme qualification and rollout phases · documented · Source date not stated · Retrieved 2026-10-21

  102. status langdock:langdock:status

    The public status page covers the app, APIs, Workflows and Integrations with history.

    Components and history · documented · Source date not stated · Retrieved 2026-10-21

  103. Terms of Use | Langdock langdock:langdock:terms-20261026

    Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

    Sections 6/7/9/12/15/16/19 and Appendix 1 · documented · Source date not stated · Retrieved 2026-10-26

  104. Langdock imprint and contact point langdock:langdock:imprint-20261026

    Users and authorities can contact support@langdock.com in German and English; the imprint identifies Langdock GmbH in Berlin.

    Contact Point for Users and Authorities · documented · Source date not stated · Retrieved 2026-10-26

  105. status langdock:langdock:status-20261026

    The public status page covers the app, APIs, Workflows and Integrations with history.

    Components and history · documented · Source date not stated · Retrieved 2026-10-26

  106. T3 Chat FAQ t3-chat:t3-chat:faq-support

    The FAQ links its official feedback board and lists support email.

    Feature requests and support · documented · Source date not stated · Retrieved 2026-10-21

  107. Langdock Workshops langdock:langdock:training

    Official workshop recordings/slides cover chat, skills, integrations, agents and workflows.

    Workshop catalogue · documented · Source date not stated · Retrieved 2026-10-21