iOL's tech stack
What does iOL use?
iOL (iolpay.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SendGrid for email delivery and Sectigo for security. Last checked .
“Simplify travel connectivity and secure payments with technology that helps hotels, travel buyers, and travel tech companies work more efficiently.”
- Industry
- Internet
- Size
- 51–200 employees
- Based in
- Dubai, United Arab Emirates
- Founded
- 1998
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
iOL'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
1 tool, what the product is built with
Data & Observability
3 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Ads & Pixels
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
Security & Compliance
iOL tech stack FAQ
What tools does iOL use?
We've found 11 tools at iOL (iolpay.com). Edge & Hosting: GoDaddy. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, SendGrid and Sectigo. Last checked October 6, 2026.
What email provider does iOL use?
iOL uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does iOL use?
iOL uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does iOL use Microsoft 365?
Yes. We found Microsoft 365 at iOL through DNS verification records and email records. Microsoft 365 is used by 685,127 companies we track.
How does runsonwhat know what iOL uses?
We read public traces only: iOL'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.