Texas Pioneer Title's tech stack
What does Texas Pioneer Title use?
Texas Pioneer Title (tptitle.com) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Inspectlet for analytics and WordPress for its website. Last checked .
- Industry
- Real Estate
- Size
- 51–200 employees
- Based in
- Allen, United States
- Founded
- 2004
- Company page
- Tools found
- 9
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Texas Pioneer Title's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
1 tool, where the bytes are served from
DNS
Application
5 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Workspace
Texas Pioneer Title tech stack FAQ
What tools does Texas Pioneer Title use?
We've found 9 tools at Texas Pioneer Title (tptitle.com). Edge & Hosting: GoDaddy. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Inspectlet. Go-to-market: WordPress. Company Ops: Microsoft 365. Last checked October 6, 2026.
What email provider does Texas Pioneer Title use?
Texas Pioneer Title uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Texas Pioneer Title use?
Texas Pioneer Title uses Inspectlet for analytics. We found Inspectlet through website code.
What CMS does Texas Pioneer Title use?
Texas Pioneer Title uses WordPress for its website. We found WordPress through website code.
Does Texas Pioneer Title use Microsoft 365?
Yes. We found Microsoft 365 at Texas Pioneer Title through email records. Microsoft 365 is used by 685,717 companies we track.
How does runsonwhat know what Texas Pioneer Title uses?
We read public traces only: Texas Pioneer Title's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.