Ørsted's tech stack
What does Ørsted use?
Ørsted (orsted.com) uses at least 24 tools we can see from public records, including Microsoft 365 for email and documents, Google Tag Manager for analytics, Pardot for marketing and web-vitals for monitoring. Last checked .
- Industry
- Energy
- Size
- 5,001–10,000 employees
- Based in
- Denmark
- Founded
- 1972
- Tools found
- 24
- Categories
- 11
- Layers
- 4 of 5
- Last checked
- Oct 2026
Ørsted'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
2 tools, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Monitoring
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Company Ops
17 tools, what the team runs on day to day
Email Delivery
Collaboration
Dev Tools
Finance & Legal
Ørsted tech stack FAQ
What tools does Ørsted use?
We've found 24 tools at Ørsted (orsted.com). Application: jQuery and Anthropic. Data & Observability: Google Tag Manager, web-vitals and Dynatrace. Go-to-market: Pardot. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 2, 2026.
What email provider does Ørsted use?
Ørsted uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through email records, DNS verification records and website code.
What analytics tools does Ørsted use?
Ørsted uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
What marketing software does Ørsted use?
Ørsted uses Pardot for marketing. We found Pardot through DNS verification records, email records and website code.
Does Ørsted use Microsoft 365?
Yes. We found Microsoft 365 at Ørsted through email records, DNS verification records and website code. Microsoft 365 is used by 682,950 companies we track.
How does runsonwhat know what Ørsted uses?
We read public traces only: Ørsted'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.