Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Kore.ai, Inc. · kore.ai

Report an error on this page Is this your product? →

Link to this page

Kore.ai: AI-assisted analysis on whats-best.ai Kore.ai: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Kore.ai at a glance

Vendor
Kore.ai, Inc.
Headquarters
Not stated on the vendor’s pages as of 10 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates Kore.ai 2.5/5, the mean of 6 judges. Kore.ai's agent platform scores highest where its documentation is deepest: administration and access at 6-7, on SSO over OpenID Connect, SAML and WS-Federation, directory sync, custom admin and bot roles, and per-module permissions. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Kore.ai alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Kore.ai's agent platform scores highest where its documentation is deepest: administration and access at 6-7, on SSO over OpenID Connect, SAML and WS-Federation, directory sync, custom admin and bot roles, and per-module permissions. Data use and training lands uniformly at 4 — the privacy notice states customer data is not used for internal training or to train generalized AI models, with retention as instructed by the customer. The weak areas rest on shared evidence. Sovereignty spans the widest range, 1 to 3: the rationales record the Orlando, Florida contracting entity and the privacy notice's disclosure that personal information may be transferred to, stored in, or processed in the United States and India; higher scores credit the GDPR sections and the stated processor role, while lower ones weigh that we found no public information on EU hosting, a subprocessor list, or a data processing agreement. Processing and models scores 2-3 — we found no public information naming the models behind the platform or where inference runs. We found no public prices; only the Trial, Developer and Enterprise edition names appear.

Report an error

Speaks for it

  • Deep, documented access controls: SSO over OpenID Connect, SAML and WS-Federation with directory sync and custom admin and bot roles
  • Privacy notice commits that customer data is not used for internal training or to train generalized AI models, with retention as instructed by the customer (data use and training scores 4)
  • Broad pre-built action library — ServiceNow, Salesforce, Zendesk, HubSpot, JIRA, Freshservice, Confluence, Microsoft Graph — with no data exchanged until an action is authorized
  • Pre-release quality testing documented: K-fold cross-validation with precision, recall and F1, confusion matrices and batch testing before publishing
  • Bring-your-own-key encryption keeps encryption-key ownership with the customer through AWS KMS with HSM-backed keys

Report an error

Held against it

  • Contracting entity is Kore.ai, Inc. of Orlando, Florida, and the privacy notice says personal information may be transferred to, stored in, or processed in the United States and India
  • We found no public information naming the models behind the platform or where inference runs
  • We found no public information on a data processing agreement, a subprocessor list, or retention periods for chats and files
  • We found no public information on human approval before consequential actions, on run logs, or on schedules and triggers for agents
  • We found no public prices — only the Trial, Developer and Enterprise edition names appear

Report an error

Best for

  • You run an IT-governed deployment and need deep access controls — SSO across three protocols, directory sync and granular per-module permissions
  • Your team wants agents that create and update records in ServiceNow, Zendesk, Salesforce and Jira under scoped customer authorization
  • You validate quality before go-live and want documented K-fold cross-validation, confusion matrices and batch testing
  • You must retain ownership of encryption keys through AWS KMS in the vendor's public cloud

Report an error

Avoid if

  • You must evidence EU hosting, a subprocessor list or a data processing agreement for a European deployment
  • You need published prices to forecast cost before engaging sales
  • You need documented human approval before consequential agent actions, or per-run logs, in writing
  • You must know which models power the platform and where inference runs

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Data use, training & retention

Show reasoning
How this is scored

What happens to prompts, uploaded files, connected data and outputs: whether any of it trains a model (the vendor's or a model provider's), how long it is kept and where logs live, whether zero-retention is available, and whether a data processing agreement covers it.

0 — No statement on training or retention; the privacy policy is a website policy that does not cover the product.

3 — A general statement that business data is "not used for training", with no word on retention, on the model providers behind the product or on logs.

5 — Business data excluded from training by contract, retention periods stated for chats and files, and a DPA offered to business customers.

8 — No-training commitments stated for the vendor and every model provider it routes to, retention configurable by the admin (including deletion of chat history), zero-data-retention terms with the model providers named, and abuse-monitoring retention described.

10 — Data use fully accounted for: training, retention, logging and abuse monitoring stated per model provider, customer-controlled retention and deletion with an audit trail, outputs and connected data treated as customer data in the DPA, and an independent audit (SOC 2, ISO 27001 or ISO 42001) covering the product.

Report an error

The Head of IT

The privacy notice commits that customer data is not used for internal training, knowledge-base updates, or to train generalized AI models, keeps customer data only as instructed in the customer agreement, and is candid that information may be sent to third-party models the customer configures. But we found no public information on a data processing agreement, on retention periods for chats and files, or on zero-retention terms with the model providers behind the platform — gaps I would have to close contractually before an 800-seat rollout. 2

Report an error

The Data Protection Officer

The privacy notice commits that customer data is not used for internal training, knowledge-base updates or to train generalized AI models, keeps customer data only as instructed in the customer agreement, and states Kore.ai acts as the customer's processor under a GDPR section. What holds it back: we found no public information on a data processing agreement, on zero-data-retention terms with the model providers, or on how long logs and chat history are kept. 2

Report an error

The Automation Lead

The privacy policy states plainly that customer data is not used for internal training or to train the generalized models offered with the service, and retention of customer data follows the customer's instructions in the agreement. But we found no public information on stated retention periods for chats and files, on what third-party model providers keep when a customer routes to them, or on a data processing agreement, so a buyer cannot pin down the full retention picture. 2

Report an error

The Customer-Service Director

The privacy notice commits that customer data is not used to train models, that retention follows the customer's instructions in the customer agreement, and that the vendor acts as the customer's processor — a workable start for call transcripts. But I found no public information on retention periods for chats and files, on a data processing agreement, or on what the third-party model providers do with data the customer routes to them, which is where my agents' conversations would land. 2

Report an error

The Works Council Member

The privacy notice states in plain words that customer data is not used to train generalised AI models or for internal enhancements, and retention follows the customer agreement — a commitment I can welcome in writing. But there is no word on how long chats and files are actually kept, whether prompts are logged anywhere, what the third-party models a customer may connect do with the data, or a data processing agreement on file, so the record a co-determination would rest on stays incomplete. 2

Report an error

The Skeptic

The privacy notice commits that customer data is not used for internal training or to train generalized models, and retention is "as instructed by the customer" in the customer agreement — a deferral, not stated periods for chats and files. It admits information may be sent to a third-party model "as configured by the customer", but we found no public information on what those providers do with prompts, on a data processing agreement, or on abuse-monitoring retention. 2

Report an error

Models & processing location

Show reasoning
How this is scored

Which models sit behind the product and who runs them, where inference and storage happen, whether the customer can pin processing to the EU, choose or exclude model providers, bring its own model or key, or run the product in its own cloud or on premises.

0 — The models behind the product and the processing location are not stated.

3 — The model family is named, but where inference runs and through which provider (the model maker, a hyperscaler, the vendor) is unstated.

5 — Models and their providers named, with an EU processing option stated for storage and at least the default model.

8 — Each available model listed with provider and inference region, EU-only processing selectable by the admin and enforced across models, model providers excludable, and bring-your-own-key or own-cloud deployment documented.

10 — Processing fully under the customer's control and documented: EU-only or on-premises inference for every feature including agents and connectors, open-weight or self-hosted models supported, data flows per feature published, and a residency commitment in the contract rather than on a marketing page.

Report an error

The Head of IT

We found no public information naming the models behind the platform or where inference runs; OpenAI and Azure OpenAI appear only as customer-configured integration templates. The only locational facts are personal-information transfers to the United States and India and an AWS-hosted public cloud SaaS, alongside bring-your-own-key for AWS KMS and a passing reference to an on-premises installation, with no statement of an EU processing option or how on-premises deployment is actually obtained. 2 4 5 8

Report an error

The Data Protection Officer

OpenAI and Azure OpenAI are documented as integrations the customer authorizes with its own API key, and the privacy notice discloses transfers to the United States and India for processing and storage. We found no public information on an EU processing option, on inference regions for any model, or on how an on-premises deployment is actually obtained — the encryption-key guide describes Kore's public cloud SaaS, and the on-premises mention is a passing note in the NLU documentation. 8 2 5 4

Report an error

The Automation Lead

No page names the models that power the platform's own features or where inference runs; OpenAI and Azure OpenAI appear only as integrations a customer wires up itself. The privacy policy says personal information may be transferred to and processed in the United States and India, self-hosting appears only as a passing reference, and the encryption setup guide assumes the public cloud — I cannot pin processing anywhere, let alone to the EU, and bring-your-own-key here means encryption keys, not model keys. 2 4 5 8

Report an error

The Customer-Service Director

Personal information may be transferred to and processed in the United States and India, the platform runs in the vendor's public cloud with encryption keys manageable through AWS KMS, and an on-premises installation gets a passing mention with a pointer to support. Which models sit behind the assistants and where inference runs are not stated, and I found no EU processing option. 2 4 5

Report an error

The Works Council Member

We found no public information naming the models behind the product or where inference runs; OpenAI and Azure OpenAI appear only as integrations a customer may authorise, not as the product's own model stack. What the pages do show is that personal information may be transferred to and processed in the United States and India, that encryption keys can stay in the customer's own AWS key management, and that an on-premises installation is mentioned in passing with no description of how a customer obtains or runs it. 2 4 5 8

Report an error

The Skeptic

We found no public information naming the models behind the platform or where inference runs; the privacy notice says personal information may be transferred to, stored in, or processed in the United States and India, and the encryption setup runs through AWS. An on-premises installation gets a passing mention only as a configurable setting, with nothing on how a customer obtains or runs it. 2 4 5

Report an error

Admin, identity & access controls

Show reasoning
How this is scored

What the IT department controls: SSO and SCIM provisioning, roles and groups, which models, agents and connectors each group may use, retrieval that respects the permissions of the source system, audit logs, usage reporting, and policies such as data-loss prevention — and whether reporting on staff use is scoped and documented.

0 — No admin features documented; accounts are individual sign-ups.

3 — A team workspace with an owner and member invitations, but no SSO, no roles and no audit log.

5 — SSO, admin and member roles, user management, and an admin view of usage.

8 — SAML/OIDC SSO with SCIM provisioning, group-based permissions for models, agents and connectors, retrieval that inherits source-system permissions, exportable audit logs, and usage analytics with documented scope.

10 — Governance a regulated company can operate: fine-grained policies (DLP, content filters, prompt and output logging rules), audit logs streamed to a SIEM, per-agent ownership and approval, usage reporting that can be aggregated or pseudonymised for works-council agreements, and every admin action logged.

Report an error

The Head of IT

The strongest area for an IT department: single sign-on over OpenID Connect, SAML and WS-Federation, SAML attribute sync that updates group and role assignments on every sign-in, custom admin and bot roles assignable to users or groups, granular bot permissions, directory sync, a fifteen-minute admin session timeout, and a Master Admin who can view and run audit reports and bot chat history. We found no public information on SCIM provisioning by that name, retrieval that inherits source-system permissions, or exportable and streamable audit logs for a SIEM, which is what would move this to enterprise-operable. 6 7

Report an error

The Data Protection Officer

Single sign-on over SAML, OpenID Connect and WS-Federation with SAML attribute sync mapping groups and roles at login, a full role model with custom admin and bot roles, Full/View/No permission levels per bot area, and Master Admin permissions covering audit reports and bot chat history. We found no public information on SCIM provisioning by name, group policies scoped to models or connectors, exportable audit logs, or the documented scope of usage analytics. 6 7

Report an error

The Automation Lead

This is solid IT territory: single sign-on over SAML, OpenID Connect and WS-Federation with group and role assignments synced from SAML attributes, directory sync for enrollment, custom admin and bot roles with full/view/none permissions per module, and audit reports plus bot chat history locked behind the Master Admin. It sits below the top band because we found no public information on retrieval inheriting source-system permissions, export of audit logs to a SIEM, or the documented scope of usage reporting. 6 7

Report an error

The Customer-Service Director

Single sign-on over SAML, OpenID Connect and WS-Federation, directory sync, custom admin and bot roles assignable to users or groups, and granular permissions per bot area including batch testing and usage analytics — close to what my IT team needs to govern forty agents' tooling. I found no public information on SCIM provisioning by name, exportable audit logs, or retrieval that inherits the permissions of the source system. 6 7

Report an error

The Works Council Member

Role administration is genuinely deep: single sign-on over OpenID Connect, SAML and WS-Federation, SAML attribute sync that drives group and role assignment, custom admin and bot roles with per-module permissions, a master-admin permission over audit reports and bot chat history, and a fifteen-minute idle timeout on admin sessions. Two gaps matter from my side — the scope of usage analytics is not documented as aggregatable or pseudonymised for works-council purposes, and admin access to staff chat history is stated without any corresponding written logging or anonymisation rules. 6 7

Report an error

The Skeptic

This is documented in unusual depth: SSO over OpenID Connect, SAML and WS-Federation with directory sync and attribute-driven role assignment, custom admin and bot roles, Full/View/No permissions per bot module, and Master Admin access to audit reports and bot chat history. We found no public information on whether retrieval inherits source-system permissions or whether audit logs can be exported and streamed, which keeps it below the top of the range. 6 7

Report an error

Integrations, connectors & knowledge

Show reasoning
How this is scored

How the product reaches company knowledge and systems: connectors to file stores, wikis, mail, CRM, ticketing and ERP, how fast and how completely they sync, the API, support for open protocols such as MCP, and how the assistant cites the sources it answers from.

0 — No integrations; users paste text or upload files one at a time.

3 — File upload and one or two connectors (for example a drive), with no API and no statement on sync or citations.

5 — A connector library covering the common file stores, wikis and collaboration tools, answers citing sources, and a documented API.

8 — Connectors to file stores, wikis, mail, CRM and ticketing with incremental sync, custom connectors or MCP support, an API and webhooks for embedding assistants and agents in other tools, and source citations on every grounded answer.

10 — The product sits in the company's systems: read and write connectors with documented scopes, MCP servers and clients, contact-centre or telephony integration where relevant, a knowledge layer that can be audited and corrected, and the data, agents and configuration exportable when the customer leaves.

Report an error

The Head of IT

The action library is broad and real — Salesforce, HubSpot, Zendesk, Freshdesk, Freshservice, ServiceNow, Jira, BambooHR, Microsoft Graph and Confluence among them, with OAuth 2.0, API key and Basic auth, pre-built dialog tasks and a low-code interface, and a default posture of no data exchange until an integration is authorized. But these are outbound actions rather than documented knowledge sync: we found no public information on sync speed or completeness, on source citations for grounded answers, or on MCP support. 8 9

Report an error

The Data Protection Officer

A broad pre-built action library — ServiceNow, Salesforce, Zendesk, HubSpot, JIRA, Freshdesk, Freshservice, Confluence, Microsoft Graph, Stripe and more — with OAuth 2.0 and API-key configuration per connector, a low-code interface for custom API integrations, and no data exchanged with any integration until an action is explicitly authorized. We found no public information on sync cadence, MCP support, or source citations on answers. 8 9

Report an error

The Automation Lead

The pre-built action library is what I build agents on: ServiceNow, Jira, Zendesk, Freshdesk, Freshservice, Salesforce, HubSpot, Microsoft Graph and Confluence with documented OAuth scopes, including write actions like creating tickets, issues and leads, with OAuth 2.0, basic and API-key auth, low-code flow templates and default-deny until an action is authorized. We found no public information on MCP, sync frequency, source citations on answers or webhooks, which keeps it off the top band. 8 9 6

Report an error

The Customer-Service Director

Pre-built actions with read-write templates for Zendesk, Freshdesk, Freshservice and ServiceNow tickets, Salesforce and HubSpot CRM, Stripe payments and Confluence pages, each authorized through OAuth 2.0 I can scope, with no data exchanged until I authorize an action — exactly the order and ticket actions I want. Sync cadence, source citations on grounded answers and MCP support are not documented on the pages captured. 8 9

Report an error

The Works Council Member

The connector library is broad — Confluence, Jira, ServiceNow, Salesforce, Zendesk, HubSpot, Microsoft Graph, BambooHR and more — each with pre-built action templates, OAuth or API-key authorisation, and a default that nothing flows until an action is explicitly authorised. We found no public information on how the connectors sync, how answers cite their sources, on MCP support, or on a documented API for embedding the assistant in other tools. 8 9

Report an error

The Skeptic

The actions library is broad and real — ServiceNow, Salesforce, Zendesk, HubSpot, JIRA, Freshservice, Confluence, Microsoft Graph and more, with create, update and delete verbs and OAuth — and by default the assistant exchanges data with nothing until an action is authorized. We found no public information on sync speed or completeness, on source citations for grounded answers, or on MCP and API support in the captured pages. 8 9

Report an error

Agent capabilities & guardrails

Show reasoning
How this is scored

What an agent can actually do and where it stops: multi-step tasks, tool use and actions in other systems, scheduling and triggers, human approval before consequential actions, run logs, evaluation and testing before release, and the limits the vendor states rather than hides.

0 — No agents; the product is a chat window, whatever the marketing says.

3 — Saved prompts or custom assistants with instructions and files, but no actions in other systems and no run history.

5 — Agents that call tools or APIs and run multi-step tasks, built without code, with a log of each run.

8 — Agents that act in connected systems with scoped permissions, human approval configurable per action, triggers and schedules, test and evaluation tooling before release, and documented limits and failure handling.

10 — Agents a business can put in production and account for: versioning and staged rollout, evaluation against test sets, monitoring of quality and cost per agent, handover to a human with full context, every action attributable to the agent and the person who deployed it, and the vendor's own statement of what agents must not be trusted with.

Report an error

The Head of IT

Bots run multi-step dialog tasks that create, update and delete records in connected systems, are built low-code, exchange no data with any integration until authorized, and have chat history viewable by the Master Admin; NLP work can be tested with K-fold cross-validation, a confusion matrix and batch testing before publishing. We found no public information on configurable human approval before consequential actions, on triggers and schedules, or on per-agent monitoring, versioning and failure handling — the guardrails I would insist on before letting agents touch production systems. 4 6 8

Report an error

The Data Protection Officer

Agents run dialog tasks that act in connected business systems via pre-built action templates, built low-code, with K-fold cross-validation, confusion-matrix review and batch testing before a bot is published, and integrations stay inert until authorized. We found no public information on run logs, human approval before consequential actions, or schedules and triggers for agent execution. 8 4 6 10

Report an error

The Automation Lead

Agents run multi-step dialog tasks against those integrations with default-deny action authorization, publishing is a gated permission, and the test-before-rollout story is genuinely deep: K-fold cross-validation with configurable K, precision, recall and F1 per fold, confusion matrices, an ML graph comparing development against published state, batch testing and CSV export. But on my production must-haves — a configurable human approval step before a consequential action, schedules and triggers, and documented per-run logs and failure handling — we found no public information. 4 6 8

Report an error

The Customer-Service Director

Agents act in connected systems under scoped customer authorization, and evaluation before go-live is genuinely documented: K-fold cross-validation reporting precision, recall and F1, a confusion matrix, ML graphs and batch testing, with the honest limit that K-fold is unavailable for few-shot and zero-shot models. I found no public information on human approval before consequential actions, on schedules and triggers, or on how a conversation hands over to my human agents with its full context beyond a permission entry that mentions "Agent Transfer". 4 6 8 10

Report an error

The Works Council Member

Actions can genuinely act in other systems — creating Jira issues, sending emails through Microsoft Graph, creating Salesforce leads — each gated by a scoped authorisation the administrator configures, and with K-fold cross-validation, confusion matrices and batch testing available before a bot is published. But there is no documented human approval per action at run time, no run log, and no vendor statement of what agents must not be trusted with; until those are in writing, an agent writing to a colleague's BambooHR record stays a co-determination case, not a routine deployment. 8 4 6 10

Report an error

The Skeptic

Agents act in connected systems through individually authorized actions with multi-step dialog tasks, and there is genuine pre-release testing — K-fold cross-validation, a confusion matrix, batch testing and a publish gate — more than most "agent" products show. We found no public information on human approval before consequential actions, on schedules or triggers, on run logs, or on any vendor-stated limits on what agents may be trusted with. 4 6 8

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where customer data is hosted, and who the subprocessors are — model providers above all, then hosting, search, telephony and email. Independently sourced by the sovereignty pipeline; for an AI product the model provider is a subprocessor, so a European interface over a non-European model counts as such.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors (including model providers) unnamed.

3 — A privacy policy exists, but hosting location is unstated or non-EU and the model providers behind the product are not named as subprocessors.

5 — EU hosting stated and an EU contracting entity, but prompts reach non-EU model providers or other subprocessors without a stated safeguard or EU region.

8 — EU hosting on named infrastructure, EU contracting entity, every subprocessor listed with its location including model providers, EU inference available, and a DPA offered.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and model processing, every subprocessor European or optional, data export and deletion documented, and a security or certification statement published rather than implied.

Report an error

The Head of IT

Kore.ai, Inc. is a Florida entity, the privacy notice states personal information may be transferred to, stored in and processed in the United States and India, and hosting is otherwise unstated; we found no public information on an EU contracting entity, EU hosting, or a subprocessor list naming the model providers. A GDPR and UK GDPR section and an acknowledgement that Kore.ai acts as the customer's processor exist, which is worth something, but there is no stated safeguard for a European deployment. 2 5

Report an error

The Data Protection Officer

The contracting entity is Kore.ai, Inc. of Orlando, Florida, personal information may be transferred to and processed in the United States and India, and the platform's public cloud SaaS runs on AWS infrastructure. We found no public information on EU hosting, on a subprocessor list naming the model providers, or on a data processing agreement — for a European deployment that is the decisive gap. 2 5

Report an error

The Automation Lead

The contracting entity is Kore.ai, Inc. of Orlando, Florida, the privacy policy states personal information may be transferred to and processed in the United States and India, and the platform account we saw sits on AWS. We found no public information on an EU hosting option, a subprocessor list naming the model providers, or a data processing agreement. 2 5

Report an error

The Customer-Service Director

The contracting entity is Kore.ai, Inc. of Orlando, Florida, and the privacy notice itself says personal information may be transferred to, stored in or processed in the United States and India; GDPR and UK GDPR sections exist, but hosting is not confirmed on the vendor's own pages. No subprocessor list including the model providers is published, and I found no EU hosting, EU inference or DPA information — material for a European contact-centre buyer. 2 5

Report an error

The Works Council Member

The contracting entity is Kore.ai, Inc. of Orlando, Florida, and the privacy notice says personal information may be transferred to and processed in the United States and India, with AWS the only infrastructure that can be inferred from the pages. We found no public information on EU hosting, on a subprocessor list including model providers, or on a data processing agreement, so nothing captured here evidences European data control. 2 5

Report an error

The Skeptic

The contracting entity is Kore.ai, Inc. of Orlando, Florida, the privacy notice places processing in the United States and India, and we found no public information naming the subprocessors — the model providers behind the platform above all — or confirming an EU hosting option or a data processing agreement. A detailed privacy policy exists; European sovereignty does not. 2 5

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
How this is scored

Whether a company can compute the real annual cost from public pages alone: price per seat, per agent, per conversation or per usage unit, what is included in each tier, usage limits and overage, which models, connectors or agents cost extra, minimum seats and term.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or "from" figure exists, but usage limits, included models and what scales the cost are unclear.

5 — Prices per tier are public with the main inclusions, but usage limits, overage, agent runs or enterprise features (SSO, audit logs, EU processing) are unpriced or "on request".

8 — Every tier priced publicly with seat or usage units, usage limits and overage rates, add-ons listed, minimum seats and term stated.

10 — Complete price computability: annual cost derivable for a given number of seats, agents or conversations, with every usage rate, model surcharge, add-on and support tier and the cancellation and data-return terms published.

Report an error

The Head of IT not rated — no public information

We found no public information on pricing — no seat or usage prices, tiers, included models, usage limits or minimum terms — in the vendor homepage, the agent platform page or the documentation captures I read; the only pricing-adjacent fact is that bring-your-own-key requires an active Kore.ai subscription. Budgeting this for eight hundred staff would be a sales conversation, not a computation. 1 5 10

Report an error

The Data Protection Officer not rated — no public information

We found no public information on pricing: no seat, tier or usage figures appear on the homepage, the AI agent platform page, or any of the documentation pages we read, so a company cannot compute an annual cost from the captured pages. 1 10

Report an error

The Automation Lead

We found no public price information in the pages we read — no seat or usage figures, tiers or limits — so no annual cost can be computed. The only pricing-adjacent facts are that encryption-key control requires an active subscription with the feature enabled, and that the Confluence connector's authorization depends on the target product's edition. 1 5 9

Report an error

The Customer-Service Director not rated — no public information

We found no public pricing on the pages captured: no per-seat, per-conversation or usage figures anywhere, only edition names (Trial, Developer, Enterprise) and a subscription requirement for the bring-your-own-key feature. My CFO could not forecast a cost per conversation from what is published here. 1 5 9

Report an error

The Works Council Member

We found no public prices on the captured pages; the only pricing-adjacent facts are that an active subscription is a prerequisite for bring-your-own-key encryption and that editions named Developer, Enterprise and Trial exist, without any figures. A buyer cannot compute an annual cost from what is published here. 5 9

Report an error

The Skeptic not rated — no public information

We found no public information on pricing in the captured pages — no seat, usage or tier prices, no inclusions, no minimums or term. The only pricing-adjacent fact is that Developer and Enterprise editions exist alongside a trial, with nothing on what any of them cost. 1 9 10

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

Only a passing reference in the documentation (S6 likewise mentions 'on-prem accounts'); no page describes how a customer obtains or runs an on-premises deployment, and the BYOK guide assumes Kore's public cloud SaaS.

1/1 pts 4 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Kore.ai

Is Kore.ai European?

Not determined: the vendor’s pages as captured do not say where Kore.ai is based.

Where does Kore.ai store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

Does Kore.ai have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

What are the best alternatives to Kore.ai?

As of 18 Nov 2026, the panel rates Langdock (4/5), Dust (3.5/5) and Unique AI (3.5/5) highest among the other 23 AI Agents & Assistants products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Langdock (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Kore.ai alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (10)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page kore.ai Checked 10 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage kore.ai Checked 10 Nov 2026 Details →
  3. 3 Data use, training & retention — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  4. 4 Models & processing location — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  5. 5 Models & processing location — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  6. 6 Admin, identity & access controls — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  7. 7 Admin, identity & access controls — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  8. 8 Integrations, connectors & knowledge — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  9. 9 Integrations, connectors & knowledge — found from sitemap developer.kore.ai Checked 10 Nov 2026 Details →
  10. 10 Agent capabilities & guardrails — found from sitemap www.kore.ai Checked 10 Nov 2026 Details →