runsonwhat

San Francisco Bay Guardian's tech stack

What does San Francisco Bay Guardian use?

San Francisco Bay Guardian (sfbg.com) uses at least 9 tools we can see from public records, including Google Workspace for email and documents and WordPress for its website. Last checked .

Tools found
9
Categories
6
Layers
3 of 5
Last checked
Oct 2026

San Francisco Bay Guardian'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.

Application

4 tools, what the product is built with

Go-to-market

4 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

San Francisco Bay Guardian tech stack FAQ

What tools does San Francisco Bay Guardian use?

As of October 2026, runsonwhat has found 9 tools at San Francisco Bay Guardian (sfbg.com) in public records. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress, Yoast SEO and Google Ad Manager. Company Ops: Google Workspace. Last checked October 31, 2026.

What email provider does San Francisco Bay Guardian use?

San Francisco Bay Guardian uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on sfbg.com. Google Workspace is used by 406,769 companies runsonwhat tracks.

What is San Francisco Bay Guardian's website built with?

San Francisco Bay Guardian uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on sfbg.com. WordPress is used by 603,422 companies runsonwhat tracks.

Does San Francisco Bay Guardian use jQuery?

Yes. runsonwhat found jQuery at San Francisco Bay Guardian through jQuery code on sfbg.com. jQuery is a Frontend tool used by 925,302 companies runsonwhat tracks.

How does runsonwhat know what San Francisco Bay Guardian uses?

runsonwhat reads public records only. Of the 9 tools at San Francisco Bay Guardian, 6 were found through code on sfbg.com, 1 through DNS records, 1 through email records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and sfbg.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.