ERR's tech stack
What does ERR use?
ERR (err.ee) uses at least 18 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Industry
- Media Production
- Size
- 201–1,000 employees
- Based in
- Tallinn, Estonia
- Founded
- 1955
- Company page
- Tools found
- 18
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
ERR'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
Hosting & Cloud
CDN & Edge
Application
4 tools, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
7 tools, what the team runs on day to day
Workspace
Dev Tools
Security & Compliance
ERR tech stack FAQ
What tools does ERR use?
We've found 18 tools at ERR (err.ee). Edge & Hosting: Cloudflare and Google Cloud. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Chartbeat. Go-to-market: Google Ads. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 7, 2026.
What cloud does ERR run on?
ERR uses Google Cloud for hosting. We found Google Cloud through DNS records.
What email provider does ERR use?
ERR uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does ERR use?
ERR uses Google Analytics, Google Tag Manager and Chartbeat for analytics. We found Google Analytics through website code.
Does ERR use jQuery?
Yes. We found jQuery at ERR through website code. jQuery is used by 764,325 companies we track.
How does runsonwhat know what ERR uses?
We read public traces only: ERR'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.