Satakunnan Osuuskauppa's tech stack
What does Satakunnan Osuuskauppa use?
Satakunnan Osuuskauppa (satakunnanosuuskauppa.fi) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, Amazon CloudFront for content delivery and Usercentrics for security. Last checked .
- Industry
- Retail
- Size
- 1,001–5,000 employees
- Based in
- Finland
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Satakunnan Osuuskauppa'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
3 tools, where the bytes are served from
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Satakunnan Osuuskauppa tech stack FAQ
What tools does Satakunnan Osuuskauppa use?
We've found 9 tools at Satakunnan Osuuskauppa (satakunnanosuuskauppa.fi). Edge & Hosting: Amazon Route 53, Amazon CloudFront and Amazon Web Services. Application: Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel and Google Ads. Company Ops: Usercentrics. Last checked October 3, 2026.
What cloud does Satakunnan Osuuskauppa run on?
Satakunnan Osuuskauppa uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What analytics tools does Satakunnan Osuuskauppa use?
Satakunnan Osuuskauppa uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Satakunnan Osuuskauppa use Google Analytics?
Yes. We found Google Analytics at Satakunnan Osuuskauppa through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Satakunnan Osuuskauppa uses?
We read public traces only: Satakunnan Osuuskauppa'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.