runsonwhat

Yelo Bank's tech stack

What does Yelo Bank use?

Yelo Bank (yelo.az) uses at least 18 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SendPulse for marketing and Cloudflare for content delivery. Last checked .

Industry
Banking
Size
201–1,000 employees
Based in
Baku, Azerbaijan
Founded
1994
LinkedIn
Company page
Tools found
18
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Yelo Bank'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

CDN & Edge

Application

2 tools, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

Yelo Bank tech stack FAQ

What tools does Yelo Bank use?

We've found 18 tools at Yelo Bank (yelo.az). Edge & Hosting: Cloudflare. Application: jQuery and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and TikTok Pixel. Company Ops: Microsoft 365, Atlassian and Let's Encrypt. Last checked October 4, 2026.

What email provider does Yelo Bank use?

Yelo Bank uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Yelo Bank use?

Yelo Bank uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What marketing software does Yelo Bank use?

Yelo Bank uses SendPulse for marketing. We found SendPulse through email records.

Does Yelo Bank use Microsoft 365?

Yes. We found Microsoft 365 at Yelo Bank through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Yelo Bank uses?

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