Announcing the availability of Community 14 / 2026 R1 for SaaS Customers*
*There will be a 6-month delay in supporting Self-hosted customers on v14 / 2026 R1 while we focus on upgrades and migrations of SaaS customer environments to bring them into compliance with Verint's updated support and security standards. SaaS customers with Self-hosted non-production environment are encouraged to use their v14 Staging environments for development until the official support for Self-hosted/On-Premises for 14 is available.
This release has many software and architecture updates that improve the platform.
Overview
Verint Community 14 / 2026 R1 is a new, modernized architecture as part of our AWS Application Modernization Lab (AML) program. Version 14 / 2026 R1 upgrades the platform to run on .NET Core and Linux containers, bringing the benefits of a contemporary cloud stack: better performance, easier deployments, and stronger reliability — with no new functionality or UX changes required to get there.
Top 5 Benefits for Customers
- Faster Performance: .NET Core platform runs 5x faster than v13 / 2024 R1 on the previous architecture. Container-based architecture also allows parts of the system to auto-scale on demand, with improved health monitoring and automated recovery.
- Easier, Less Disruptive Deployments: Container-based deployments make updates and upgrades more consistent and reliable, with less disruption than before. Development installation is also simplified via Docker Compose and NuGet-hosted resources.
- Improved Observability and Support: Modern, open standards for logging, tracing, and metrics give both the Verint team and on-premises customers clearer visibility into system health, making issues faster to spot and resolve.
- Faster Delivery of New Value: A move to CI/CD and GitOps automates the deployment of functional changes to production, enabling shorter release cadences and quicker delivery of improvements.
- No Disruption to Existing Customizations Done Through the UI : , widgets, automations, emails, and embeddables created through the UI carry over to v14 with no updates needed. No new functionality or UX changes are introduced between v13 and v14.
What to Expect
- All customers must upgrade and migrate to v14 / 2026 R1 to be compliant with Verint's support and security standards
- Must be on version 12.1 or later before upgrading.
- Applicable to both Self-Hosted and Verint-Hosted customers. (Self-Hosted customers will be notified when v14 2026 R1 will be released for their environments)
- Only customizations and integrations using public APIs are supported on v14.
- Integrations or plugins that require database access will be reside in custom database schemas isolated from the core database schema.
- Plugins will need to be recompiled.
- SaaS Customers will need to delegate DNS control for subdomains to Verint for ease of site upkeep and SSL Certificate management
- Outgoing Email (SMTP) for SaaS Customers is automatically setup and is no longer configurable.
Timeline
Community.Telligent.com has been running on v14 / 2026 R1 since November 2025. Partners have been working with v14 / 2026 R1 for a few months getting familiar with the updates to prepare to support customers to upgrade and migrate. There is a phased upgrade and migration plan for customers, starting with low-complexity sites, followed by medium and high complexity sites. The full migration process is expected to take 3-6 months, and will be a consultative, collaborative process between Verint, customers, and partners to ensure a smooth transition.
v14 2026 R1 Upgrade and Migration Process Overview
All customers must upgrade to v14 / 2026 R1. SaaS customers will migrate first, with Verint working alongside customers and their partners throughout the process.
Migration Steps
- Customization Inventory – Verint runs a database query to create a customer-specific inventory of nonstandard customizations that need updates to be compatible with v14.(e.g., plugins to recompile on .NET 10, API-compliant stored procedures, and tables).
- Staging Environment Setup– Verint does a backup of your current SaaS production environment and restores it to a new v14 staging site.
- Pre-Access Validation– Verint verifies that all out-of-the-box widgets and Verint-authored customizations function correctly before granting access. Custom SSO functionality may need to be disabled for Verint to access and complete its work.
- Customer Updates– You and your designated partners access the staging site to update the flagged customizations. Once validated, Verint coordinates the production deployment.
- Final Sync– Verint takes a fresh backup of your current (v 12.1 or v 13.x) production environment and applies it to the staging site to ensure everything is current.
- Go-Live– After a final review, Verint and your IT team schedule the DNS cutover to point your community domain to the new v14 environment.
For more information, please see the following resources:
