Zea's tech stack
What does Zea use?
Zea (zeaengine.com) uses at least 15 tools we can see from public records, including HubSpot for sales, Google Analytics for analytics, Stripe for payments and WordPress for its website. Last checked .
- Industry
- Software
- Based in
- Canada
- Founded
- 2015
- Company page
- Tools found
- 15
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Zea'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
CDN & Edge
Application
4 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Sales & CRM
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Zea tech stack FAQ
What tools does Zea use?
We've found 15 tools at Zea (zeaengine.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: reCAPTCHA and CleanTalk. Last checked October 4, 2026.
What CRM does Zea use?
Zea uses HubSpot for sales and CRM. We found HubSpot through website code.
What payment provider does Zea use?
Zea uses Stripe for payments. We found Stripe through website code.
What analytics tools does Zea use?
Zea uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Zea use?
Zea uses WordPress and Yoast SEO for its website. We found WordPress through website code.
What marketing software does Zea use?
Zea uses ActiveCampaign for marketing. We found ActiveCampaign through website code.
Does Zea use jQuery?
Yes. We found jQuery at Zea through website code. jQuery is used by 655,712 companies we track.
How does runsonwhat know what Zea uses?
We read public traces only: Zea'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.