runsonwhat

Almaviva Experience's tech stack

What does Almaviva Experience use?

Almaviva Experience (almavivadobrasil.com.br) uses at least 7 tools we can see from public records, including Matomo for analytics, Cloudflare for content delivery and GlobalSign for security. Last checked .

Industry
IT Services
Size
10,000+ employees
Based in
Sítio Beira Rio, Brazil
Founded
2006
LinkedIn
Company page
Re-check liveVisit almavivadobrasil.com.br
Tools found
7
Categories
4
Layers
4 of 5
Last checked
Oct 2026

Almaviva Experience'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

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

4 tools, what the team runs on day to day

Security & Compliance

Companies like Almaviva Experience also use

Tools common among companies with a similar stack that we haven't found at Almaviva Experience.

Companies with a stack like Almaviva Experience's

Ranked by shared tools, with rare tools counting more.

More IT Services companies

Other IT Services companies we've checked.

Almaviva Experience tech stack FAQ

What tools does Almaviva Experience use?

We've found 7 tools at Almaviva Experience (almavivadobrasil.com.br). Edge & Hosting: Cloudflare. Data & Observability: Matomo. Company Ops: GlobalSign, Sophos and Trend Micro. Last checked October 3, 2026.

What analytics tools does Almaviva Experience use?

Almaviva Experience uses Matomo for analytics. We found Matomo through website code.

Does Almaviva Experience use Cloudflare?

Yes. We found Cloudflare at Almaviva Experience through DNS records and email records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Almaviva Experience uses?

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