runsonwhat

academics's tech stack

What does academics use?

academics (academics.de) uses at least 19 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Sentry for monitoring. Last checked .

“academics - das führende Karriereportal für akademische Talente aus den Bereichen Wissenschaft, Forschung, Öffentliches und Gesellschaft”

Based in
Germany
Founded
2005
LinkedIn
Company page
Tools found
19
Categories
11
Layers
5 of 5
Last checked
Oct 2026

academics'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

1 tool, what the product is built with

Data & Observability

2 tools, what they measure and store

Company Ops

9 tools, what the team runs on day to day

Dev Tools

Security & Compliance

academics tech stack FAQ

What tools does academics use?

We've found 19 tools at academics (academics.de). Edge & Hosting: Google Cloud. Application: Anthropic. Data & Observability: Google Analytics and Sentry. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, Atlassian and Mailgun. Last checked October 4, 2026.

What cloud does academics run on?

academics uses Google Cloud for hosting. We found Google Cloud through DNS records.

What email provider does academics use?

academics uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does academics use?

academics uses Google Analytics for analytics. We found Google Analytics through website code.

Does academics use Microsoft 365?

Yes. We found Microsoft 365 at academics through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what academics uses?

We read public traces only: academics'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.