San Francisco AIDS Foundation's tech stack
What does San Francisco AIDS Foundation use?
San Francisco AIDS Foundation (stopaids.org) uses at least 12 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, Cloudflare for content delivery and reCAPTCHA for security. Last checked .
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
San Francisco AIDS Foundation'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
San Francisco AIDS Foundation tech stack FAQ
What tools does San Francisco AIDS Foundation use?
We've found 12 tools at San Francisco AIDS Foundation (stopaids.org). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: reCAPTCHA. Last checked October 3, 2026.
What analytics tools does San Francisco AIDS Foundation use?
San Francisco AIDS Foundation uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does San Francisco AIDS Foundation use?
San Francisco AIDS Foundation uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does San Francisco AIDS Foundation use Cloudflare?
Yes. We found Cloudflare at San Francisco AIDS Foundation through website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what San Francisco AIDS Foundation uses?
We read public traces only: San Francisco AIDS Foundation'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.