Summary

  • Toku’s UAE subsidiary entered a hosting agreement with Core42; Toku says platform onboarding has started, but the release does not identify a UAE customer or a production workload.
  • The arrangement pairs Microsoft Azure infrastructure in the UAE with Core42 controls and Toku’s CX software. Core42’s own product page limits the public-cloud offer to specified data classes, so the announced route is not proof that every regulated workload fits.

A hosting step before a customer win

Toku announced on 8 October that Toku Technology L.L.C., its UAE subsidiary, had agreed with Core42 to host the Toku platform on Core42 Sovereign Enabled Public Cloud. The agreement was marked by a signing ceremony in Abu Dhabi on 2 October. Toku says onboarding has begun.

That is a real deployment step, but a narrow one. The announcement names no UAE buyer, awarded public-sector contract, workload, revenue, fee, contract term or go-live date. It does not say that migration is complete. Toku says it is participating in several regional public-sector tenders with partners; it does not identify those tenders or say that this agreement has converted one into a customer.

The distinction matters because the offer being positioned is a customer-experience platform, not simply spare cloud capacity. Toku describes a product spanning voice, chat, email and digital channels, with AI features including transcription and summarisation. Such systems can touch interactions and recordings that a buyer may classify as sensitive. The release does not say which Toku modules, customer data or service functions are included in this onboarding.

Three suppliers sit between the data and the buyer

The announced route has three technical layers. Microsoft Azure provides the underlying cloud infrastructure deployed in the UAE. Core42 supplies the sovereign-control, governance and compliance-monitoring layer, including landing-zone architecture and oversight through Core42 Insight. Toku supplies the customer-facing application. A future customer would still choose and configure its own workload.

Core42’s product page says data is hosted in the UAE through Azure regional infrastructure, with Core42 controls and monitoring through Insight. That is the provider’s product description. The public materials do not show the agreement’s data map, who can access each layer, where support telemetry or backups go, how long interaction records are retained, or which party bears each incident and audit obligation. A regional hosting location is one part of that proof, not a substitute for it.

Core42 also draws a boundary around its public-cloud product. Its current page says the service is designed for “Open” and “Confidential/Sensitive” data, and directs workloads containing “Secret” or “Top Secret” information to its Signature Private Cloud. Toku has not disclosed the classification of the workloads being onboarded. Buyers therefore cannot infer from the press release that every government contact-centre workload is suitable for this environment.

The commercial test is conversion and repeatability

For Toku, a local hosting route may reduce one obstacle in selling CX software where procurement requires in-country infrastructure and local controls. For Core42, a software platform can add another workload to the Azure-plus-controls stack. Both are plausible commercial benefits; neither is measured in the announcement. There is no disclosed hosting price, implementation budget, customer count or comparison with Toku’s other deployment options.

The next evidence should connect infrastructure to a buyer: a named customer or award, the modules and data classes in scope, a production date, service levels and the responsibilities assigned to Toku, Core42 and the customer. The sales case also depends on whether the same deployment pattern can be reused without custom integration and compliance work erasing its cost advantage.

Until then, the news is an option being prepared, not demand proven. The agreement gives Toku a locally hosted route into UAE procurement conversations. Whether it produces paid workloads, compliant operations and a repeatable regional business remains open.

Sources