runsonwhat

InnsalzachJobs's tech stack

What does InnsalzachJobs use?

InnsalzachJobs (innsalzachjobs.de) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Google Tag Manager for analytics, Cloudflare for content delivery and SendGrid for email delivery. Last checked .

“Aktuelle Jobs aller Berufskategorien aus Altötting, Burghausen, Mühldorf, Waldkraiburg etc. · Ohne Registrierung · Jobs in der Region Innsalzach finden”

Industry
Healthcare
Size
10,000+ employees
Based in
Wasserburg Am Inn, Germany
LinkedIn
Company page
Tools found
9
Categories
7
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

1 tool, 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

4 tools, what the team runs on day to day

InnsalzachJobs tech stack FAQ

What tools does InnsalzachJobs use?

We've found 9 tools at InnsalzachJobs (innsalzachjobs.de). Edge & Hosting: Cloudflare. Application: Google Maps. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel. Company Ops: Google Workspace, SendGrid and Mailchimp Transactional. Last checked October 3, 2026.

What email provider does InnsalzachJobs use?

InnsalzachJobs uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does InnsalzachJobs use?

InnsalzachJobs uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

Does InnsalzachJobs use Cloudflare?

Yes. We found Cloudflare at InnsalzachJobs through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what InnsalzachJobs uses?

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