AWAS's tech stack
What does AWAS use?
AWAS (awas.com) uses at least 13 tools we can see from public records, including WP Engine for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Financial Services
- Size
- 51–200 employees
- Founded
- 1985
- Company page
- Tools found
- 13
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
AWAS'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
Hosting & Cloud
CDN & Edge
Application
6 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
3 tools, what the team runs on day to day
Workspace
Security & Compliance
AWAS tech stack FAQ
What tools does AWAS use?
We've found 13 tools at AWAS (awas.com). Edge & Hosting: Cloudflare and WP Engine. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Microsoft 365, Mimecast and Cookiebot. Last checked October 3, 2026.
What cloud does AWAS run on?
AWAS uses WP Engine for hosting. We found WP Engine through website code.
What email provider does AWAS use?
AWAS uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does AWAS use?
AWAS uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does AWAS use?
AWAS uses WordPress for its website. We found WordPress through website code.
Does AWAS use Microsoft 365?
Yes. We found Microsoft 365 at AWAS through DNS verification records and email records. Microsoft 365 is used by 261,146 companies we track.
How does runsonwhat know what AWAS uses?
We read public traces only: AWAS'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.