Parisons's tech stack
What does Parisons use?
Parisons (parisons.com) uses at least 15 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Food Production
- Size
- 1,001–5,000 employees
- Based in
- Calicut, India
- Company page
- Tools found
- 15
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Parisons'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
CDN & Edge
Application
4 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
7 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Parisons tech stack FAQ
What tools does Parisons use?
We've found 15 tools at Parisons (parisons.com). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics. Go-to-market: WordPress, Meta Pixel and Yoast SEO. Company Ops: Google Workspace. Last checked October 7, 2026.
What email provider does Parisons use?
Parisons uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does Parisons use?
Parisons uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Parisons use?
Parisons uses WordPress, Yoast SEO and Elementor for its website, among 5 tools in this category. We found WordPress through website code.
Does Parisons use jQuery?
Yes. We found jQuery at Parisons through website code. jQuery is used by 765,361 companies we track.
How does runsonwhat know what Parisons uses?
We read public traces only: Parisons'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.