runsonwhat

The GitHub Blog's tech stack

What does The GitHub Blog use?

The GitHub Blog (semmle.com) uses at least 15 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Azure Monitor for analytics and WordPress for its website. Last checked .

Industry
IT Services
Size
51–200 employees
Based in
San Francisco, United States
Founded
2006
LinkedIn
Company page
Re-check liveVisit semmle.com
Tools found
15
Categories
8
Layers
4 of 5
Last checked
Oct 2026

The GitHub Blog'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

Hosting & Cloud

DNS

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

4 tools, how they find and keep customers

Website & CMS

Marketing

Company Ops

6 tools, what the team runs on day to day

Workspace

Dev Tools

Security & Compliance

Companies like The GitHub Blog also use

Tools common among companies with a similar stack that we haven't found at The GitHub Blog.

Companies with a stack like The GitHub Blog's

Ranked by shared tools, with rare tools counting more.

More IT Services companies

Other IT Services companies we've checked.

The GitHub Blog tech stack FAQ

What tools does The GitHub Blog use?

As of October 2026, runsonwhat has found 15 tools at The GitHub Blog (semmle.com) in public records. Edge & Hosting: Google Cloud, NS1 and WordPress VIP. Data & Observability: Azure Monitor and FullStory. Go-to-market: WordPress, Yoast SEO and Mailchimp. Company Ops: Google Workspace, Apple Business and Let's Encrypt. Last checked October 23, 2026.

What cloud does The GitHub Blog run on?

The GitHub Blog uses Google Cloud for hosting and cloud infrastructure, alongside WordPress VIP, according to runsonwhat (October 2026). runsonwhat found Google Cloud through a subdomain that points at Google Cloud. Google Cloud is used by 75,735 companies runsonwhat tracks.

What email provider does The GitHub Blog use?

The GitHub Blog uses Google Workspace for email and office software, alongside Apple Business, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 402,311 companies runsonwhat tracks.

What analytics tools does The GitHub Blog use?

The GitHub Blog uses Azure Monitor for analytics, alongside FullStory, according to runsonwhat (October 2026). runsonwhat found Azure Monitor through Azure Monitor code on semmle.com. Azure Monitor is used by 5,392 companies runsonwhat tracks.

What is The GitHub Blog's website built with?

The GitHub Blog uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on semmle.com. WordPress is used by 596,215 companies runsonwhat tracks.

What marketing software does The GitHub Blog use?

The GitHub Blog uses Mailchimp for marketing, according to runsonwhat (October 2026). runsonwhat found Mailchimp through email records that authorize Mailchimp. Mailchimp is used by 114,914 companies runsonwhat tracks.

Does The GitHub Blog use Let's Encrypt?

Yes. runsonwhat found Let's Encrypt at The GitHub Blog through DNS records that point at Let's Encrypt. Let's Encrypt is a Security & Compliance tool used by 55,746 companies runsonwhat tracks.

Which companies have a tech stack similar to The GitHub Blog's?

The companies with the stacks most like The GitHub Blog's are M Science, The GitHub Blog, Sugra Systems and DMU, according to runsonwhat (October 2026). Each shares 3 to 10 tools with The GitHub Blog, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what The GitHub Blog uses?

runsonwhat reads public records only. Of the 15 tools at The GitHub Blog, 6 were found through DNS records, 5 through code on semmle.com, 2 through email records and 2 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and semmle.com about 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.