runsonwhat

Sveriges Radio Förvaltning's tech stack

What does Sveriges Radio Förvaltning use?

Sveriges Radio Förvaltning (srf.se) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Based in
Sweden
Tools found
9
Categories
5
Layers
4 of 5
Last checked
Oct 2026

Sveriges Radio Förvaltning'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

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Sveriges Radio Förvaltning tech stack FAQ

What tools does Sveriges Radio Förvaltning use?

We've found 9 tools at Sveriges Radio Förvaltning (srf.se). Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365. Last checked October 3, 2026.

What email provider does Sveriges Radio Förvaltning use?

Sveriges Radio Förvaltning uses Microsoft 365 for email and documents. We found Microsoft 365 through email records, DNS verification records and website code.

What analytics tools does Sveriges Radio Förvaltning use?

Sveriges Radio Förvaltning uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Sveriges Radio Förvaltning use?

Sveriges Radio Förvaltning uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Sveriges Radio Förvaltning use Microsoft 365?

Yes. We found Microsoft 365 at Sveriges Radio Förvaltning through email records, DNS verification records and website code. Microsoft 365 is used by 326,338 companies we track.

How does runsonwhat know what Sveriges Radio Förvaltning uses?

We read public traces only: Sveriges Radio Förvaltning'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.