What tech stack does FactSet use?
FactSet'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, TypeScript, JavaScript, C++, C#, Python, Java, AWS.
- Frontend
- React, TypeScript
- Backend
- C++, C#
- Cloud
- AWS, Azure
- Data
- Snowflake, SQL Server
- Critical path
- Market data, workstation performance, APIs, portfolio analytics, identifiers, and data quality
- GTM
- Salesforce, Marketo
FactSet's detected tech stack
FactSet's public stack signals a mature enterprise environment with cloud, data, AI, security, analytics, and customer-facing product systems.
- React· Frontend
- TypeScript· Frontend
- JavaScript· Frontend
- C++· Backend
- C#· Backend
- Python· Backend
- Java· Backend
- AWS· Infrastructure
- Azure· Infrastructure
- Kubernetes· Infrastructure
- Snowflake· Data
- SQL Server· Data
- Python data pipelines· Data
- Salesforce· GTM
- Marketo· GTM
- Tableau· GTM
What does FactSet use on the backend and infrastructure?
Public job postings, product disclosures, and technology partner signals point to backend and infrastructure layers including C++, C#, Python, Java 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 FactSet use on the frontend, data, or GTM tooling?
Detected public signals include frontend and data tools such as React, TypeScript, JavaScript, Snowflake, SQL Server, Python data pipelines and GTM or enterprise systems such as Salesforce, Marketo, Tableau. These signals should be confirmed in discovery because business units may use different tools.
What FactSet'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:FactSet careersBuiltWith technology lookupFactSet Q2 FY2026 results
FactSet — frequently asked questions
