TL;DR
- NICE completed its acquisition of Cognigy on 8 September 2025, and NiCE Cognigy is still sold standalone as well as inside CXone Mpower.
- Cognigy remains strong where many rivals are thin: it offers on-premise installation on Kubernetes and publishes Australian SaaS and voice regions.
- The closest like-for-like alternative is Kore.ai. PolyAI and Trillet suit teams that want the vendor to build and run agents; Parloa suits EU-regulated buyers; Amazon Connect suits AWS builders.
- Before switching, get NICE's standalone, integration and region commitments in your renewal contract.
An acquisition does not break a working platform, but it does change who sets the roadmap, and renewal is the moment buyers get to ask about it. This guide is for teams running Cognigy, or evaluating it, who want to know what to ask NICE and what the realistic alternatives look like if the answers fall short.
Vendor facts come from each company's own website, documentation, trust center or status page, checked in October 2026. Where we write "not documented," we did not find it on the pages we checked; that is a question for the vendor, not proof of absence.
What changed when NICE acquired Cognigy?
NICE closed its acquisition of Cognigy on 8 September 2025 after regulatory approvals, and the product now carries the name NiCE Cognigy. According to Cognigy's announcement, it will be offered "both as part of the unified CXone Mpower platform and as a standalone offering," and former CEO Philipp Heltewig now leads it as general manager.
What has not changed, on the vendor's own pages, is the product footprint. Cognigy's docs still describe shared SaaS, dedicated SaaS and on-premise installation, its status page still lists Australian environments, and its integration pages still name rival CCaaS platforms such as Genesys and Amazon Connect alongside NiCE CXone. Pricing remains quote-only.
What should Cognigy customers ask NICE before renewing?
The useful questions are the ones whose answers can go into a contract. Vendor roadmaps shift for many reasons, ownership included, so treat each of the following as a commitment to request in writing rather than a risk to assume.
- Is the standalone offering covered for the full term? Cognigy says it will be sold standalone and in CXone Mpower. What to do: ask for the standalone product, its support terms and its price basis to be named in the order form for the length of your contract.
- Will non-NICE CCaaS connectors stay supported? Cognigy documents Genesys (including the AudioHook connector), Amazon Connect, Avaya, Five9, Twilio, RingCentral and 8x8. What to do: if your agents sit on Genesys or Amazon Connect, list those connectors in the contract with a notice period for any deprecation.
- Will the Australian region continue? Cognigy's status page lists an Australian SaaS environment and an Australian voice gateway environment. What to do: have the region written into the agreement, not just the status page.
- What does on-premise support cover? Cognigy's prerequisites page recommends managed Kubernetes (EKS, AKS or GKE) and warns that distributions such as OpenShift "will require significant additional configuration effort," which Cognigy does not support configuring. What to do: confirm your Kubernetes distribution is in scope and who owns cluster issues.
- Who delivers changes? Cognigy is sold through a partner network, and we found no managed service on its site. What to do: confirm your implementation partner's continuity and rates before you renew.
If NICE answers all five in writing, staying avoids the cost of rebuilding agents elsewhere. If the answers are vague, or you were already stretched on Kubernetes or partner capacity, the alternatives below are worth a proper evaluation.
Which alternatives match Cognigy on deployment, hosting and integrations?
Kore.ai is the only alternative here that matches Cognigy on all three of on-premise, private cloud and a published Australian region; the others trade one of those for something else, such as vendor-managed delivery or public pricing. The matrix compares each option against the capabilities Cognigy customers most often depend on, as of October 2026.
| Capability | NiCE Cognigy | Kore.ai | PolyAI | Parloa | Trillet | Amazon Connect |
|---|---|---|---|---|---|---|
| On-premise | Yes (Kubernetes) | Yes | Not documented | Not documented | Yes (Docker) | Not documented |
| Dedicated or private cloud | Dedicated SaaS | Single-tenant VPC | Not documented | Not documented | Private cloud/VPC | Not documented |
| Published Australian region | Yes (SaaS and voice gateway) | Yes (Sydney) | "APAC"; Australia not named | No regions named | By agreement (no published region) | Yes (Sydney) |
| Genesys | Yes, incl. AudioHook | Yes, incl. AudioHook | Yes | Yes | Custom integration, scoped per engagement | Analytics connector only |
| NiCE CXone | Native | Yes | Yes | Not listed | Custom integration, scoped per engagement | Not applicable (is the CCaaS) |
| Cisco or Mitel PBX for the AI agent | Not documented | Not documented | Both named | Cisco named | Cisco CUCM and Mitel (custom integration) | Analytics connector only (Cisco UCCE) |
| Who builds the agents | You or a partner | You or an integrator | PolyAI, or you | You, on Parloa's suite | Trillet architects | You, AWS or partners |
| Pricing | Quote | Quote | Quote | Quote | Quote | $0.038/voice min plus telephony |
On attestations, Trillet holds SOC 2 Type II and ISO 27001 and sits below Cognigy, which lists ISO 27001, ISO 27701, ISO 42001, SOC 2 Type II, TISAX and BSI C5. Every alternative here states at least SOC 2 and ISO 27001. For how other platforms in the category stack up, see our best voice AI for contact centers roundup.
Kore.ai: the closest like-for-like replacement
Kore.ai is the most direct swap for a Cognigy customer, because it is also a builder platform with multi-tenant SaaS, on-premise and single-tenant VPC deployment listed in its trust center, plus an APAC (Sydney) region on its status page. It names NICE CXone, Five9, Talkdesk, Genesys (with AudioHook) and Amazon Connect, and offers its own voice gateway and bring-your-own SIP.
Delivery runs through systems integrators including Accenture, Cognizant, Infosys and Teleperformance, and through the AWS and Azure marketplaces, so the operating model will feel familiar to a partner-led Cognigy shop. Its trust center lists SOC 2 Type 2, ISO 27001, PCI DSS, GDPR and CCPA. Avaya, Cisco and Mitel were not found in its documentation, and pricing is quote-only.
Choose it if: you want to keep the same deployment options and Australian hosting, change vendor, and keep working with an integrator.
PolyAI: when you want the vendor to build and run it
PolyAI changes the operating model rather than copying it: its managed service will "design it, build it, run it on our own models," and a self-serve Agent Studio is available for teams that want to build. It names the broadest set of contact center and PBX systems in this comparison, including Avaya, Cisco, Mitel, Genesys, NICE, Five9 and Amazon Connect, and lists ISO 27001, SOC 2 Type II, HIPAA, PCI DSS and Cyber Essentials Plus.
The trade-offs sit exactly where Cognigy is strong. PolyAI is hosted on AWS with no on-premise option documented, and it lists an APAC region without naming Australia. Platform pricing is per minute but unpublished.
Choose it if: your partner bench was the bottleneck and SaaS hosting is acceptable to your security team.
Parloa: when EU regulation drives the shortlist
Parloa sells a builder suite (Agent Builder, Performance Lab, Lens and others), and its trust center reads like an EU compliance checklist: ISO 42001, DORA and the EU AI Act, on top of ISO 27001, SOC 2, PCI DSS, HIPAA and GDPR. It names Genesys, Amazon Connect, Cisco, Avaya, Five9, Talkdesk and others, plus business systems such as Salesforce, ServiceNow and SAP.
For a Cognigy customer, two gaps stand out. Parloa describes built-in data residency but names no regions, and no on-premise or private-cloud model appears on its pages. NICE is not on its native connector list, which matters if you run CXone. Pricing is quote-only and per minute for voice, with outcome-based pricing supported "when it makes sense."
Choose it if: you operate in EU financial services or another sector where DORA and the EU AI Act shape procurement, and SaaS hosting is acceptable.
Trillet: managed delivery on your own infrastructure
Trillet is the alternative for teams that liked Cognigy's on-premise option but not running the Kubernetes cluster and partner bench behind it. Trillet's solution architects design, build, deploy and manage the implementation, and it can run in the cloud, in a private cloud or VPC, or fully on-premise via Docker. The on-premise Docker deployment guide explains what that involves.
It also covers ground Cognigy does not document: its ViciDial integration is native and production-proven, and Cisco CUCM, Mitel, Avaya and Asterisk-based PBXs connect through custom SIP/CTI integration scoped per engagement. Trillet is headquartered in Australia with onshore engineering and support, and Enterprise deployments are available in any region by agreement.
Trillet loses on three points, and they are real. Cognigy publishes an Australian region while Trillet's residency is set by agreement; Cognigy lists more attestations; and Trillet has no native Genesys or NICE CXone connector; integration with either is custom work scoped per engagement. Pricing is custom per engagement, as of October 2026.
Choose it if: you need on-premise or a legacy Cisco or Mitel PBX, and you want the vendor's team, not a partner, to own delivery.
Amazon Connect: when you would rather build on AWS
Amazon Connect, now marketed as Amazon Connect Customer, is the option for teams ready to move the contact center itself onto AWS. Voice is published at $0.038 a minute, including AI self-service but not telephony. Agentic voice runs in the Asia Pacific (Sydney) region, and the service sits within AWS's IRAP PROTECTED assessment scope.
It is not a drop-in replacement for an orchestration layer that sits on top of your existing CCaaS. If your agents stay on on-premise Genesys Engage, Avaya Aura or Cisco UCCE, AWS documents that connector for analytics, not for AI self-service, and third-party AI agents connect through an API-only route. The only deployment AWS documents is its own cloud, and it notes that prices "may vary by region."
Choose it if: you are consolidating onto AWS, serve Australian government, and have engineers to build the flows.
When is staying on Cognigy the right call?
Staying on NiCE Cognigy makes sense when your contact center already runs on NICE CXone, your team operates managed Kubernetes comfortably, and your implementation partner is performing. In that situation the acquisition may simplify things, since the AI layer and the CCaaS now come from one company.
The case for moving is strongest when the renewal answers are vague, when you depend on a non-NICE CCaaS and cannot get connector commitments in writing, or when on-premise operation has become a burden your team did not plan for. What to do: run one queue on an alternative in parallel before your notice date, so the decision rests on your own call data rather than on vendor slides. For a wider view of how these vendors and agency platforms compare, use the voice AI platform comparison hub.
If on-premise deployment or a legacy PBX is the deciding factor, talk to Trillet's enterprise team about a scoped pilot.
Frequently Asked Questions
Who owns Cognigy now?
NICE owns Cognigy. The acquisition closed on 8 September 2025, and the product is now branded NiCE Cognigy. Cognigy says it is offered both standalone and as part of NICE's CXone Mpower platform.
Can I still buy Cognigy without NICE CXone?
Yes, according to the vendor. Cognigy's acquisition announcement says it will be offered both inside CXone Mpower and as a standalone offering, and its integration pages still list Genesys, Amazon Connect, Avaya and other CCaaS platforms. Put the standalone terms in your contract.
What is the closest alternative to Cognigy?
Kore.ai is the closest match on paper: it is also a builder platform delivered through partners, and it documents SaaS, on-premise and single-tenant VPC deployment plus a Sydney region. Check Avaya, Cisco and Mitel needs separately, because those were not found in its documentation.
Does Cognigy support on-premise deployment?
Yes. Cognigy documents on-premise installation on Kubernetes, recommending managed services such as EKS, AKS or GKE. Its docs warn that other distributions, such as OpenShift, need significant extra configuration that Cognigy does not support, so your team runs the cluster.
Which Cognigy alternatives host data in Australia?
Kore.ai and Amazon Connect publish Sydney regions, as does Cognigy itself. PolyAI lists an APAC region without naming Australia, Parloa names no regions, and Trillet offers data residency by agreement rather than a published region.
