What tech stack does Thomson Reuters use?
Thomson Reuters's stack is detected from public sources such as careers pages, engineering/blog content, BuiltWith, StackShare, SEC/product disclosures, and technology partner announcements. Treat it as directional: validated technologies include React, Angular, TypeScript, Java, Python, .NET, AWS, Azure.
- Frontend
- React, Angular
- Backend
- Java, Python
- Cloud
- AWS, Azure
- Data
- PostgreSQL, Elasticsearch
- Critical path
- Legal AI, search, professional content, tax workflow, Reuters news, and enterprise APIs
- GTM
- Salesforce, Adobe Experience Cloud
Thomson Reuters's detected tech stack
Thomson Reuters's public stack signals a mature enterprise environment with cloud, data, AI, security, analytics, and customer-facing product systems.
- React· Frontend
- Angular· Frontend
- TypeScript· Frontend
- Java· Backend
- Python· Backend
- .NET· Backend
- AWS· Infrastructure
- Azure· Infrastructure
- Kubernetes· Infrastructure
- PostgreSQL· Data
- Elasticsearch· Data
- Snowflake· Data
- Salesforce· GTM
- Adobe Experience Cloud· GTM
- Marketo· GTM
What does Thomson Reuters use on the backend and infrastructure?
Public job postings, product disclosures, and technology partner signals point to backend and infrastructure layers including Java, Python, .NET and AWS, Azure, Kubernetes. In a company of this scale, the practical architecture is hybrid: legacy systems, cloud workloads, data platforms, security tooling, and vendor-managed enterprise applications coexist.
What does Thomson Reuters use on the frontend, data, or GTM tooling?
Detected public signals include frontend and data tools such as React, Angular, TypeScript, PostgreSQL, Elasticsearch, Snowflake and GTM or enterprise systems such as Salesforce, Adobe Experience Cloud, Marketo. These signals should be confirmed in discovery because business units may use different tools.
What Thomson Reuters's stack means if you sell to them
The best integration angle is to fit existing cloud, identity, data, analytics, workflow, content, advertising, subscription, or engineering systems rather than forcing a rip-and-replace motion.
A displacement pitch needs a clear cost, security, speed, AI, or consolidation case; an integration pitch should show clean APIs, procurement readiness, enterprise controls, and measurable adoption by the buyer's operating team.
As of June 2026.Sources:Thomson Reuters careersBuiltWith technology lookupThomson Reuters FY2025 results
Thomson Reuters — frequently asked questions
