runsonwhat

San Francisco Public Library's tech stack

What does San Francisco Public Library use?

San Francisco Public Library (sfpl.org) uses at least 21 tools we can see from public records, including Pantheon for hosting, Emma for marketing, Fastly for content delivery and OneTrust for security. Last checked .

Industry
Libraries
Size
201–1,000 employees
Based in
San Francisco, United States
Founded
1878
LinkedIn
Company page
Tools found
21
Categories
13
Layers
5 of 5
Last checked
Nov 2026

San Francisco Public Library's stack, layer by layer

Of 21 tools, 11 came from website code, 7 from DNS verification records and 3 from email records. 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

Hosting & Cloud

CDN & Edge

Application

5 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

Email Delivery

Collaboration

Finance & Legal

Security & Compliance

San Francisco Public Library tech stack FAQ

What tools does San Francisco Public Library use?

As of November 2026, runsonwhat has found 21 tools at San Francisco Public Library (sfpl.org) in public records. Edge & Hosting: Fastly and Pantheon. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Meta Pixel and Emma. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked November 2, 2026.

What cloud does San Francisco Public Library run on?

San Francisco Public Library uses Pantheon for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found Pantheon through Pantheon code on sfpl.org. Pantheon is used by 4,324 companies runsonwhat tracks.

What email provider does San Francisco Public Library use?

San Francisco Public Library uses Microsoft 365 for email and office software, alongside Apple Business, according to runsonwhat (November 2026). runsonwhat found Microsoft 365 through email records that authorize Microsoft 365 and code on sfpl.org. Microsoft 365 is used by 727,856 companies runsonwhat tracks.

What analytics tools does San Francisco Public Library use?

San Francisco Public Library uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on sfpl.org. Google Analytics is used by 905,186 companies runsonwhat tracks.

What marketing software does San Francisco Public Library use?

San Francisco Public Library uses Emma for marketing, according to runsonwhat (November 2026). runsonwhat found Emma through a DNS verification record for Emma. Emma is used by 2,761 companies runsonwhat tracks.

Does San Francisco Public Library use jQuery?

Yes. runsonwhat found jQuery at San Francisco Public Library through jQuery code on sfpl.org. jQuery is a Frontend tool used by 928,867 companies runsonwhat tracks.

Does San Francisco Public Library use AI tools?

Yes. runsonwhat has found OpenAI at San Francisco Public Library; OpenAI, for example, through a DNS verification record for OpenAI. AI services called only from servers leave no public trace, so San Francisco Public Library may use more AI tools than these.

Which companies have a tech stack similar to San Francisco Public Library's?

The companies with the stacks most like San Francisco Public Library's are delvag portal, Avis Budget Sp. Z O. O., Nordea Liv and CLA Global: International Accounting Network, according to runsonwhat (November 2026). Each shares 4 to 9 tools with San Francisco Public Library, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what San Francisco Public Library uses?

runsonwhat reads public records only. Of the 21 tools at San Francisco Public Library, 11 were found through code on sfpl.org, 7 through DNS records and 3 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and sfpl.org 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.