runsonwhat

Portal UEA's tech stack

What does Portal UEA use?

Portal UEA (uea.edu.br) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, WordPress for its website and GlobalSign for security. Last checked .

“Universidade do Estado do Amazonas”

Industry
Software
Size
1,001–5,000 employees
Based in
United States
Founded
2015
LinkedIn
Company page
Re-check liveVisit uea.edu.br
Tools found
11
Categories
6
Layers
3 of 5
Last checked
Oct 2026

Portal UEA'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.

Application

3 tools, what the product is built with

Frontend

Media & UI

Go-to-market

3 tools, how they find and keep customers

Website & CMS

Marketing

Company Ops

5 tools, what the team runs on day to day

Workspace

Security & Compliance

Companies like Portal UEA also use

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

Companies with a stack like Portal UEA's

Ranked by shared tools, with rare tools counting more.

Portal UEA tech stack FAQ

What tools does Portal UEA use?

We've found 11 tools at Portal UEA (uea.edu.br). Application: jQuery, Vimeo and ResponsiveVoice. Go-to-market: WordPress and All in One SEO. Company Ops: Microsoft 365, Google Workspace and GlobalSign. Last checked October 3, 2026.

What email provider does Portal UEA use?

Portal UEA uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What CMS does Portal UEA use?

Portal UEA uses WordPress and All in One SEO for its website. We found WordPress through website code.

Does Portal UEA use Microsoft 365?

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

How does runsonwhat know what Portal UEA uses?

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