Thomson Reuters Regulatory Intelligence Sold to CUBE: What Customers Should Do Now

Thomson Reuters sold its Regulatory Intelligence business (TRRI), together with the Oden state-rules products, to CUBE: announced May 16, 2024, completed December 31, 2024, terms undisclosed. CUBE has now published the switch: its migration FAQs say that if your renewal falls on or after November 1, 2026, you move to CUBE Intel on or by that date and access to your existing TRRI subscription ends, and Thomson Reuters' own TRRI sign-in page says the product will migrate to CUBE by December 31, 2026. The product decision is being made for you. The contract decision is not: that is still your renewal date and notice period.

Audit your contract this week, export your alert history and audit trail before access to the old subscription ends, whatever you decide, and score CUBE Intel against at least one independent alternative in a 30 to 60 day parallel run before your notice window closes.

Below are a six-phase migration decision checklist and a comparison of the vendors you are likely to evaluate, with the one column that changes fastest in this market: who owns whom, as of September 30, 2026.

The deal closed December 31, 2024, and the old product line now points to CUBE

CUBE announced the acquisition of TRRI and the Oden businesses (State Rules and Regulations, Policy Terminator/Sentry PT, OdenTrack) on May 16, 2024, and described a combined base of approximately 1,000 customers in banking, insurance, asset and investment management, payments and adjacent regulated industries. It announced completion on January 2, 2025, saying the deal had closed on December 31, 2024, that its headcount had grown to nearly 700, and that it now counted more than 200 enterprise customers (around 40% of Tier 1 financial institutions, by CUBE's count) and nearly 800 mid-market customers. On April 8, 2025, CUBE launched RegPlatform Intel for the mid-market, describing it as bringing together CUBE's enhanced capabilities after the Reg-Room and TRRI and Oden acquisitions. The product has been renamed since: CUBE now markets it as CUBE Intel, or simply Intel in its product menu.

Nearly two years on, the migration is visible in the plumbing. As of September 30, 2026, CUBE's own product line is RegPlatform, Oden, Intel and PoweredBy, and the TRRI name does not appear in it. The old Thomson Reuters regulatory intelligence product page answers with a permanent redirect to CUBE's website, and the TRRI sign-in page carries a banner reading "Thomson Reuters Regulatory Intelligence will be migrating to CUBE by 31 December 2026," linked to CUBE's migration page for Thomson Reuters Regulatory Intelligence and Reg-Track customers. A legacy TRRI landing page is still live on a Thomson Reuters domain and does not mention CUBE. CUBE's press releases do not give the dates, but its migration FAQs do (see the next section). Its recent news is about partnerships and new capabilities, such as a collaboration with IBM announced on September 16, 2026.

Customers' integrations tell the same story. In the ServiceNow community, a customer wrote in September 2025 that everything was still labeled as Thomson Reuters, including the store app. On May 5, 2026, a ServiceNow employee answered that the connector "remains active" and recommended engaging directly with CUBE about end-user license terms. CUBE announced its own certified ServiceNow connector on April 14, 2026, and its migration FAQs say all existing TRRI contracts were assigned to CUBE on December 31, 2024. Licensing questions about the feed now belong with CUBE, so get the answers in writing.

The sale also moved the Cost of Compliance benchmark many boards quote. CUBE Research published The Cost of Compliance Report 2025 on November 4, 2025, drawing on more than 2,000 senior compliance, risk and legal leaders across 11 markets. The last edition before the sale, Thomson Reuters Regulatory Intelligence's 2023 report, surveyed more than 350 practitioners. The franchise survives, but the respondent base changed shape entirely; treat any year-over-year trendline across the sale as broken. As of September 30, 2026, CUBE has published a Q1 2026 update but no full 2026 edition.

CUBE has set the switchover dates, and your renewal date decides which ones apply

CUBE does not put the dates in its press releases. They sit in the migration FAQs it publishes for TRRI customers, split by renewal date (as checked on October 1, 2026):

• Renewal before November 1, 2026 (FAQs): you keep your existing subscription until your renewal date, then move to CUBE Intel by accepting a new CUBE order form. Your existing contract ends when access to the existing subscription ends.
• Renewal on or after November 1, 2026 (FAQs): CUBE said it would give early access to CUBE Intel no later than August 2026, and it upgrades you on or by November 1, 2026, when access to your existing subscription ends. You stay on your existing contract until your renewal date, when you are re-contracted to CUBE, and CUBE invoices for service from November 1, 2026.

Thomson Reuters' sign-in page gives the outer bound: TRRI "will be migrating to CUBE by 31 December 2026." The FAQs say your customer success manager will confirm the exact switchover period, so get your own dates in writing. Behind the dates sit the ordinary mechanics of a private-equity-backed acquisition strategy: CUBE's March 2024 investment from Hg funded a run of acquisitions, and consolidations of this type tend to move platforms and pricing at renewal, not by press release.

That splits the urgency in two. The product switch is on CUBE's calendar, and for renewals from November 1, 2026 onward it falls on or before that date. The levers a CCO actually controls are contractual: the notice period, the auto-renew trigger, the right to export historical data before access to the old subscription ends, and the evidence that monitoring happened continuously through the switch. Miss the notice date and you have chosen to stay, on whatever terms CUBE offers. That is why the checklist below starts with the contract, not with a vendor shortlist.

The migration decision pack treats the switch as an auditable compliance event

In my read of how supervision works, regulators do not penalize firms for changing monitoring vendors; they penalize coverage gaps and missing evidence. So the decision pack is built the way an auditor will later read it: every phase produces a filed artifact. Part A is the checklist; Part B is the vendor comparison two sections down. Copy both into a sheet with an evidence-tracking column.

Phase 1: Contract and commercial audit

• Renewal date and notice period (put the notice date in your compliance calendar today)
• Auto-renew trigger and how far in advance it fires
• Change-of-control or assignment clause: CUBE says all TRRI contracts were assigned to it on December 31, 2024, so check what your clause allowed and whether anyone on your side consented in writing
• Price protection at renewal (caps, committed pricing)
• Committed term remaining and early-termination cost

Evidence to file: current contract and novation correspondence.

Phase 2: Usage inventory

• Modules actually in use: regulatory news and analysis, rulebook content, State Rules and Regulations (Oden), alert routing, Cost of Compliance benchmarking, data feeds, any GRC connector
• Named users versus active users
• Jurisdictions and regulators on your watchlist
• Downstream systems consuming the feed

Evidence to file: usage export and integration diagram.

Phase 3: Data and evidence continuity

• Export historical alerts, saved searches and taxonomies before access to the old subscription ends
• Export the audit trail proving monitoring occurred in past periods
• Confirm a retention format your auditors accept
• Identify anything that exists only inside TRRI

Evidence to file: export files and retention log.

Phase 4: Stay-versus-move evaluation

• Score a demo of CUBE's current product (CUBE Intel or RegPlatform) against the same parity sheet as every alternative: the incumbent gets no free pass and no penalty
• Compare license terms offered on a CUBE-issued license against your legacy TRRI terms, clause by clause
• Get roadmap commitments in writing, in the order form, not the deck

Evidence to file: scored parity sheet.

Phase 5: Parallel-run pilot (30 to 60 days)

• Run the incumbent and one challenger on the identical watchlist
• Count items caught, missed and duplicated, per source
• Measure time-to-alert per source
• Require visible reasoning for every triage decision: if the tool cannot say why it suppressed an item, you cannot defend the suppression later

Evidence to file: pilot scorecard.

Phase 6: Cutover and regulator-readiness

• Document the vendor change and the coverage plan for the switchover window
• Obtain sign-off from the compliance owner and the risk owner
• Update the compliance monitoring procedure text that names the tool

Evidence to file: cutover memo.

Eight ownership deals in 28 months have outdated many of the "alternatives" lists still ranking

A verification note first. On the live CUBE site, the page for the TRRI acquisition release shows a date of December 16, 2024, but the release itself, as distributed on PR Newswire, is datelined London, May 16, 2024. Regulator and vendor pages do this constantly (a website migration or republication rewrites the date), and it is the same trap that catches monitoring tools, so the timeline below cites press-release datelines, not page-render dates.

As a result, the auto-generated directories and older listicles that still rank recommend 4CRisk and Reg-Room as CUBE or TRRI alternatives, Compliance.ai as an independent option, and Regology as an independent one. None of the four is independent today. If Compliance.ai was on your shortlist, read our Compliance.ai alternatives guide: the Archer acquisition changes that evaluation the same way the CUBE deal changes this one.

Legal AI vendors have also started selling monitoring as a feature. Legora launched Monitors on June 2, 2026, citing "10,000+ official primary sources across 100+ jurisdictions," after buying the horizon-scanning platform Graceview in May. Harvey announced Horizon Scanning on September 1, 2026, citing more than 12,000 sources across 100+ jurisdictions, and describes it as available in early access to Harvey customers. If your team already works in one of those platforms, expect to be asked why you need a separate tool, and run them through the same parallel-run scorecard.

The vendor comparison: who-owns-whom is the column that changes fastest

This is the alternatives comparison, Part B of the decision pack. Two disclosures before you read it. First, RegWatch is my company; judge that row with appropriate skepticism. Second, the description and coverage columns are vendors' own words from their own sites as reviewed on September 30, 2026, and we have not independently verified any of the numbers. Where a vendor publishes prices, we cite them; where a pricing page shows none, we say so. Among the other vendors below, only Bloomberg Regology's site shows list prices for a paid plan, and only for US coverage; we reviewed Wolters Kluwer's product page through an archived copy.

RegWatch's row deserves the same skepticism. The 136 jurisdictions, their regulators and 57 topics are what RegWatch has mapped, not a statement about what any customer monitors. Every other coverage figure in the table is a vendor's own number, which is the reason to test coverage on your regulators in the parallel run, not to compare counts. For a broader look at the category beyond the TRRI lens, including tools we would not recommend for this specific migration, see Best Regulatory Horizon Scanning Tools in 2026, Compared.

The verdict by segment: only Tier 1 rulebook customers should default to staying

Each of the four segments below gets a definite call.

Tier 1 institutions standardized on CUBE rulebook content: stay, but renegotiate now. If your firm is among the enterprise customers CUBE cited at completion and your dependency is deep rulebook and inventory content, migration cost likely exceeds migration benefit. Staying is the rational call, provided you use the acquisition to negotiate: a multi-year price cap, a contractual data-export warranty, and roadmap commitments written into the order form. You will never have a better negotiating moment than the first renewal after an acquisition.

Mid-market TRRI customers moving to CUBE Intel: parallel-run before you renew. You are migrating either way, to CUBE Intel or to a challenger, because CUBE Intel is a new product, launched in April 2025, not the TRRI you bought. That makes the switching-cost argument for staying the weakest it will ever be. Run Phase 5 of the checklist with CUBE Intel as one candidate (CUBE's FAQs offer early access) and one independent vendor as the other, on your real watchlist, and let the scorecard decide.

Firms that bought TRRI primarily as a feed into a GRC platform: your connector and export formats decide, not the feature list. Before renewal, get written confirmation of connector support and test a full export. If you are untangling which layer of the stack you actually bought (the feed, the analysis or the change workflow), Regulatory Intelligence vs Horizon Scanning vs Change Management breaks the regulatory intelligence stack apart.

Teams that need published pricing, per-item explainability or a deployment in their own cloud account: this is the segment we built RegWatch for. RegWatch is not a rulebook library and does not replace TRRI's editorial content. What it replaces is the monitoring-and-triage layer: scheduled monitoring runs against the regulators and sources you choose, triage that scores each item against your company profile and writes plain-language "Why this matters" for what it accepts, and suppressed findings kept on record. Put those records through Phase 5 alongside every other candidate. If your regulator or your board requires the data plane in your own cloud account, the Private VPC deployment keeps it there, on AWS, Microsoft Azure, Google Cloud, IBM Cloud, Oracle Cloud or another provider, with outbound HTTPS to model providers still required.

A 30 to 60 day parallel run answers what no demo can

Vendor demos in this market, ours included, tend to show the same things: a clean feed, a tidy taxonomy and a headline jurisdiction count. None of that tells you what the tool misses, because misses are invisible in a demo. A parallel run makes them visible: same watchlist, same period, two tools, and a scorecard counting caught, missed, duplicated and time-to-alert per source, plus the reasoning behind every triage decision, because an unexplained suppression cannot be defended later.

We would rather be evaluated this way than by a slide, and that is the reason we will not put a platform statistic in this article. Ask any vendor, including us, to show you the same scorecard on your own regulators.

On TRRI paper today, two dates matter: CUBE's switchover and your notice date

A mid-market firm still on TRRI paper has four things to do, in order. Pull the contract this week, calendar the notice date and get CUBE to confirm your switchover date in writing; those are the two deadlines in this story. Export the alert archive and audit trail before access to the old subscription ends, whatever the eventual decision, because evidence continuity is cheap now and expensive later. Run the 30 to 60 day parallel pilot with CUBE Intel and one independent challenger on the identical watchlist. Decide 90 days before the notice date where the calendar still allows it, with the scorecard filed where the auditor will find it.

Eight ownership deals in 28 months are reason enough to date-stamp everything you rely on, including any alternatives list.

This article is general information, not legal advice.