Ceres Brewery's tech stack
What does Ceres Brewery use?
Ceres Brewery (ceres.dk) uses at least 8 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Tag Manager for analytics and SendGrid for email delivery. Last checked .
- Industry
- Beverage
- Based in
- Denmark
- Founded
- 1856
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Ceres Brewery'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
1 tool, where the bytes are served from
Hosting & Cloud
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Ceres Brewery tech stack FAQ
What tools does Ceres Brewery use?
We've found 8 tools at Ceres Brewery (ceres.dk). Edge & Hosting: Microsoft Azure. Application: Google Fonts, Next.js and Adobe Fonts. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel. Company Ops: Microsoft 365 and SendGrid. Last checked October 2, 2026.
What cloud does Ceres Brewery run on?
Ceres Brewery uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain, DNS records and website code.
What email provider does Ceres Brewery use?
Ceres Brewery uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Ceres Brewery use?
Ceres Brewery uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
Does Ceres Brewery use Microsoft 365?
Yes. We found Microsoft 365 at Ceres Brewery through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Ceres Brewery uses?
We read public traces only: Ceres Brewery'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.