runsonwhat

iPay Holding's tech stack

What does iPay Holding use?

iPay Holding (ipayholding.com) uses at least 15 tools we can see from public records, including Microsoft Azure for hosting, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Industry
Venture Capital & Private Equity
Size
201–1,000 employees
Based in
United Arab Emirates
Founded
2007
LinkedIn
Company page
Tools found
15
Categories
9
Layers
5 of 5
Last checked
Oct 2026

iPay Holding'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

Application

6 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Security & Compliance

iPay Holding tech stack FAQ

What tools does iPay Holding use?

We've found 15 tools at iPay Holding (ipayholding.com). Edge & Hosting: Cloudflare and Microsoft Azure. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress, Meta Pixel and Yoast SEO. Company Ops: reCAPTCHA and SendGrid. Last checked October 7, 2026.

What cloud does iPay Holding run on?

iPay Holding uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain, DNS records and website code.

What analytics tools does iPay Holding use?

iPay Holding uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does iPay Holding use?

iPay Holding uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.

Does iPay Holding use jQuery?

Yes. We found jQuery at iPay Holding through website code. jQuery is used by 761,740 companies we track.

How does runsonwhat know what iPay Holding uses?

We read public traces only: iPay Holding'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.