Flowerdocs's tech stack
What does Flowerdocs use?
Flowerdocs (flowerdocs.com) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, HubSpot CMS for its website and Cloudflare for content delivery. Last checked .
- Industry
- Software
- Size
- 51–200 employees
- Based in
- Paris, France
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Flowerdocs'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
3 tools, where the bytes are served from
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
3 tools, what the team runs on day to day
Security & Compliance
Flowerdocs tech stack FAQ
What tools does Flowerdocs use?
We've found 9 tools at Flowerdocs (flowerdocs.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Data & Observability: Google Analytics. Go-to-market: HubSpot CMS. Company Ops: Let's Encrypt, Google Trust Services and Amazon Trust Services. Last checked October 6, 2026.
What cloud does Flowerdocs run on?
Flowerdocs uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What analytics tools does Flowerdocs use?
Flowerdocs uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Flowerdocs use?
Flowerdocs uses HubSpot CMS for its website. We found HubSpot CMS through custom domain and website code.
Does Flowerdocs use Google Analytics?
Yes. We found Google Analytics at Flowerdocs through website code. Google Analytics is used by 574,375 companies we track.
How does runsonwhat know what Flowerdocs uses?
We read public traces only: Flowerdocs'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.