runsonwhat

Barmeniagothaer's tech stack

What does Barmeniagothaer use?

Barmeniagothaer (barmeniagothaer.de) uses at least 9 tools we can see from public records, including Storyblok for its website, LinkedIn for marketing and consentmanager for security. Last checked .

Industry
Insurance
Size
1–10 employees
Based in
Köln, Germany
Founded
2024
LinkedIn
Company page
Re-check liveVisit barmeniagothaer.de
Tools found
9
Categories
7
Layers
3 of 5
Last checked
Oct 2026

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

1 tool, what the product is built with

Frontend

Go-to-market

4 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Company Ops

4 tools, what the team runs on day to day

Collaboration

Dev Tools

Security & Compliance

Companies like Barmeniagothaer also use

Tools common among companies with a similar stack that we haven't found at Barmeniagothaer.

Companies with a stack like Barmeniagothaer's

Ranked by shared tools, with rare tools counting more.

More Insurance companies

Other Insurance companies we've checked.

Barmeniagothaer tech stack FAQ

What tools does Barmeniagothaer use?

We've found 9 tools at Barmeniagothaer (barmeniagothaer.de). Application: Vue.js. Go-to-market: Meta Pixel, LinkedIn and Storyblok. Company Ops: Atlassian, Figma and consentmanager. Last checked October 4, 2026.

What CMS does Barmeniagothaer use?

Barmeniagothaer uses Storyblok for its website. We found Storyblok through website code.

What marketing software does Barmeniagothaer use?

Barmeniagothaer uses LinkedIn for marketing. We found LinkedIn through DNS verification records.

Does Barmeniagothaer use Meta Pixel?

Yes. We found Meta Pixel at Barmeniagothaer through DNS verification records. Meta Pixel is used by 63,585 companies we track.

How does runsonwhat know what Barmeniagothaer uses?

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