Fire & Flower's tech stack
What does Fire & Flower use?
Fire & Flower (potguide.com) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Mailchimp for marketing and Amazon SES for email delivery. Last checked .
- Industry
- Cannabis
- Based in
- United States
- Founded
- 2013
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Fire & Flower'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
Application
1 tool, what the product is built with
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Fire & Flower tech stack FAQ
What tools does Fire & Flower use?
We've found 12 tools at Fire & Flower (potguide.com). Edge & Hosting: Amazon Route 53. Application: Adobe Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Meta Pixel and Mailchimp. Company Ops: Google Workspace and Amazon SES. Last checked October 4, 2026.
What email provider does Fire & Flower use?
Fire & Flower uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Fire & Flower use?
Fire & Flower uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does Fire & Flower use?
Fire & Flower uses Mailchimp for marketing. We found Mailchimp through email records.
Does Fire & Flower use Google Analytics?
Yes. We found Google Analytics at Fire & Flower through website code. Google Analytics is used by 341,711 companies we track.
How does runsonwhat know what Fire & Flower uses?
We read public traces only: Fire & Flower'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.