Get Bartender's tech stack
What does Get Bartender use?
Get Bartender (getbartender.com) uses at least 17 tools we can see from public records, including one.com for hosting, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Hospitality
- Size
- 51–200 employees
- Based in
- Copenhagen, Denmark
- Founded
- 2013
- Company page
- Tools found
- 17
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Get Bartender'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
6 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Get Bartender tech stack FAQ
What tools does Get Bartender use?
We've found 17 tools at Get Bartender (getbartender.com). Edge & Hosting: Cloudflare and one.com. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Cookiebot. Last checked October 8, 2026.
What cloud does Get Bartender run on?
Get Bartender uses one.com for hosting. We found one.com through email records.
What analytics tools does Get Bartender use?
Get Bartender uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Get Bartender use?
Get Bartender uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Get Bartender use jQuery?
Yes. We found jQuery at Get Bartender through website code. jQuery is used by 600,560 companies we track.
How does runsonwhat know what Get Bartender uses?
We read public traces only: Get Bartender'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.