Bagger Dave's's tech stack
What does Bagger Dave's use?
Bagger Dave's (baggerdaves.com) uses at least 9 tools we can see from public records, including HostGator for hosting, Microsoft 365 for email and documents, Toast for payments and WordPress for its website. Last checked .
- Industry
- Food
- Size
- 1–10 employees
- Based in
- Traverse City, United States
- Founded
- 2008
- Company page
- Tools found
- 9
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Bagger Dave's'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
Hosting & Cloud
Application
5 tools, what the product is built with
Frontend
Payments & Billing
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Workspace
Bagger Dave's tech stack FAQ
What tools does Bagger Dave's use?
We've found 9 tools at Bagger Dave's (baggerdaves.com). Edge & Hosting: HostGator. Application: jQuery, Google Fonts and Font Awesome. Go-to-market: WordPress and Elementor. Company Ops: Microsoft 365. Last checked October 4, 2026.
What cloud does Bagger Dave's run on?
Bagger Dave's uses HostGator for hosting. We found HostGator through email records.
What email provider does Bagger Dave's use?
Bagger Dave's uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What payment provider does Bagger Dave's use?
Bagger Dave's uses Toast for payments. We found Toast through website code.
What CMS does Bagger Dave's use?
Bagger Dave's uses WordPress and Elementor for its website. We found WordPress through website code.
Does Bagger Dave's use Microsoft 365?
Yes. We found Microsoft 365 at Bagger Dave's through email records and website code. Microsoft 365 is used by 685,704 companies we track.
How does runsonwhat know what Bagger Dave's uses?
We read public traces only: Bagger Dave's'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.