runsonwhat

SourceKnowledge's tech stack

What does SourceKnowledge use?

SourceKnowledge (sourceknowledge.com) uses at least 17 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, WordPress for its website and Ortto for marketing. Last checked .

Industry
Internet
Size
11–50 employees
Based in
Montreal, Canada
Founded
2009
LinkedIn
Company page
Tools found
17
Categories
11
Layers
4 of 5
Last checked
Oct 2026

SourceKnowledge'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

Application

6 tools, what the product is built with

Go-to-market

4 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

SourceKnowledge tech stack FAQ

What tools does SourceKnowledge use?

We've found 17 tools at SourceKnowledge (sourceknowledge.com). Edge & Hosting: Cloudflare and Amazon Route 53. Application: jQuery, Google Fonts and YouTube. Go-to-market: WordPress, Yoast SEO and Zendesk. Company Ops: Google Workspace, reCAPTCHA and SendGrid. Last checked October 6, 2026.

What email provider does SourceKnowledge use?

SourceKnowledge uses Google Workspace for email and documents. We found Google Workspace through email records.

What does SourceKnowledge use for customer support?

SourceKnowledge uses Zendesk for customer support. We found Zendesk through custom domain.

What CMS does SourceKnowledge use?

SourceKnowledge uses WordPress and Yoast SEO for its website. We found WordPress through website code.

What marketing software does SourceKnowledge use?

SourceKnowledge uses Ortto for marketing. We found Ortto through email records.

Does SourceKnowledge use jQuery?

Yes. We found jQuery at SourceKnowledge through website code. jQuery is used by 761,408 companies we track.

How does runsonwhat know what SourceKnowledge uses?

We read public traces only: SourceKnowledge'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.