runsonwhat

Linkfire A/S's tech stack

What does Linkfire A/S use?

Linkfire A/S (bio.to) uses at least 6 tools we can see from public records, including HubSpot CMS for its website, Google Workspace for email and documents and Cloudflare for content delivery. Last checked .

Based in
Copenhagen, Denmark
LinkedIn
Company page
Tools found
6
Categories
6
Layers
4 of 5
Last checked
Nov 2026

Linkfire A/S's stack, layer by layer

Of 6 tools, 3 came from website code, 1 from DNS verification records, 1 from email records and 1 from other records. 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

Application

1 tool, what the product is built with

Media & UI

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Linkfire A/S tech stack FAQ

What tools does Linkfire use?

As of November 2026, runsonwhat has found 6 tools at Linkfire (bio.to) in public records. Edge & Hosting: Cloudflare and Amazon Route 53. Application: Lottie. Go-to-market: HubSpot CMS. Company Ops: Google Workspace. Last checked November 8, 2026.

What email provider does Linkfire use?

Linkfire uses Google Workspace for email and office software, according to runsonwhat (November 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 416,567 companies runsonwhat tracks.

What is Linkfire's website built with?

Linkfire uses HubSpot CMS for its website, according to runsonwhat (November 2026). runsonwhat found HubSpot CMS through HubSpot CMS code on bio.to. HubSpot CMS is used by 34,193 companies runsonwhat tracks.

Does Linkfire use Cloudflare?

Yes. runsonwhat found Cloudflare at Linkfire through Cloudflare code on bio.to. Cloudflare is a CDN & Edge tool used by 729,482 companies runsonwhat tracks.

How does runsonwhat know what Linkfire uses?

runsonwhat reads public records only. Of the 6 tools at Linkfire, 3 were found through code on bio.to, 2 through DNS records and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and bio.to about 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.