What tech stack does Stewart Information Services use?
Stewart Information Services's stack is detected from public sources such as filings, company product pages, engineering or career signals, and third-party technology indexes. It is directional, so vendors should validate live tools during discovery.
- Frontend
- React
- Backend
- Java
- Cloud
- Microsoft Azure, AWS
- Data
- SQL Server, Power BI
- Critical path
- Title insurance
- GTM/ops
- Salesforce, ServiceNow
Stewart Information Services's detected tech stack
These technologies are public-signal detections for Stewart Information Services; validate current production use during discovery.
- Microsoft Azure· Infrastructure
- AWS· Infrastructure
- Salesforce· GTM / operations
- ServiceNow· GTM / operations
- Java· Backend / AI
- React· Frontend / mobile
- SQL Server· Data
- Oracle· Data
- Power BI· Data
- Okta· Infrastructure
What does Stewart Information Services use on the backend and infrastructure?
Stewart Information Services's public signals point to enterprise cloud, data, security, and workflow infrastructure rather than a single monolithic stack. The detected stack includes Microsoft Azure, AWS, Salesforce, ServiceNow, Java, React, SQL Server, Oracle.
Because the company operates regulated, transaction-heavy, or customer-facing workflows, reliability, auditability, data lineage, access control, and integration quality are likely more important than novelty.
What does Stewart Information Services use on the frontend, data, or GTM tooling?
The detected front-end, analytics, and operations signals include Java, React, SQL Server, Oracle, Power BI, Okta. These signals suggest a mix of customer-facing applications, internal workflow tools, analytics layers, and GTM systems.
For sales discovery, confirm which systems are corporate standards, which are business-unit tools, and which are legacy platforms inherited through acquisitions.
What Stewart Information Services's stack means if you sell to them
Integration-led pitches should map to the systems that already run customer, agent, borrower, claims, title, servicing, finance, or collections workflows. Strong wedge products reduce manual work, improve data quality, lower risk, or make existing cloud and CRM investments more productive.
Displacement pitches need evidence that the current tool creates measurable friction. Adjacent or workflow-specific integrations are usually easier than replacing a core system in a regulated public-company environment.
As of June 2026.Sources:Stewart 2025 Form 10-KStewart executive teamStewart investor relations
Stewart Information Services — frequently asked questions
