Heathkit's tech stack
What does Heathkit use?
Heathkit (heathkit.com) uses at least 11 tools we can see from public records, including IONOS for hosting, Microsoft 365 for email and documents, Zendesk for customer support and Shopify for its website. Last checked .
- Industry
- Radio Electronics
- Size
- 11–50 employees
- Based in
- United States
- Founded
- 1926
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Heathkit'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
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Company Ops
1 tool, what the team runs on day to day
Workspace
Heathkit tech stack FAQ
What tools does Heathkit use?
We've found 11 tools at Heathkit (heathkit.com). Edge & Hosting: Cloudflare and IONOS. Application: Vimeo, YouTube and Google Maps. Data & Observability: Bugsnag. Go-to-market: Zendesk and Shopify. Company Ops: Microsoft 365. Last checked October 4, 2026.
What cloud does Heathkit run on?
Heathkit uses IONOS for hosting. We found IONOS through email records.
What email provider does Heathkit use?
Heathkit uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What does Heathkit use for customer support?
Heathkit uses Zendesk for customer support. We found Zendesk through website code.
What CMS does Heathkit use?
Heathkit uses Shopify for its website. We found Shopify through custom domain and website code.
Does Heathkit use Microsoft 365?
Yes. We found Microsoft 365 at Heathkit through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Heathkit uses?
We read public traces only: Heathkit'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.