Leadinfo's tech stack
What does Leadinfo use?
Leadinfo (visitorqueue.com) uses at least 19 tools we can see from public records, including Google Workspace for email and documents, Stripe for payments, WordPress for its website and G2 for marketing. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- London, Canada
- Founded
- 2018
- Company page
- Tools found
- 19
- Categories
- 13
- Layers
- 4 of 5
- Last checked
- Oct 2026
Leadinfo'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
7 tools, what the product is built with
Frontend
Payments & Billing
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Leadinfo tech stack FAQ
What tools does Leadinfo use?
We've found 19 tools at Leadinfo (visitorqueue.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and Font Awesome. Go-to-market: WordPress, Meta Pixel and Rank Math. Company Ops: Google Workspace, SendGrid and iubenda. Last checked October 6, 2026.
What email provider does Leadinfo use?
Leadinfo uses Google Workspace for email and documents. We found Google Workspace through email records.
What payment provider does Leadinfo use?
Leadinfo uses Stripe for payments. We found Stripe through DNS verification records.
What CMS does Leadinfo use?
Leadinfo uses WordPress and Rank Math for its website. We found WordPress through website code.
What marketing software does Leadinfo use?
Leadinfo uses G2 for marketing. We found G2 through website code.
Does Leadinfo use jQuery?
Yes. We found jQuery at Leadinfo through website code. jQuery is used by 589,320 companies we track.
How does runsonwhat know what Leadinfo uses?
We read public traces only: Leadinfo'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.