SAS Shoes's tech stack
What does SAS Shoes use?
SAS Shoes (sasshoes.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Zoho for sales, Google Tag Manager for analytics and UptimeRobot for monitoring. Last checked .
- Industry
- Retail
- Size
- 1,001–5,000 employees
- Based in
- San Antonio, United States
- Founded
- 1976
- Company page
- Tools found
- 11
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
SAS Shoes'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
2 tools, where the bytes are served from
CDN & Edge
Application
1 tool, what the product is built with
Media & UI
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Workspace
SAS Shoes tech stack FAQ
What tools does SAS Shoes use?
We've found 11 tools at SAS Shoes (sasshoes.com). Edge & Hosting: Cloudflare and Amazon Route 53. Application: Adobe Fonts. Data & Observability: Google Tag Manager and UptimeRobot. Go-to-market: Meta Pixel and Zoho. Company Ops: Microsoft 365, Mailgun and Proton Mail. Last checked October 2, 2026.
What CRM does SAS Shoes use?
SAS Shoes uses Zoho for sales and CRM. We found Zoho through email records.
What email provider does SAS Shoes use?
SAS Shoes uses Microsoft 365 and Proton Mail for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does SAS Shoes use?
SAS Shoes uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
Does SAS Shoes use Microsoft 365?
Yes. We found Microsoft 365 at SAS Shoes through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what SAS Shoes uses?
We read public traces only: SAS Shoes'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.