SourceForge's tech stack
What does SourceForge use?
SourceForge (sf.net) uses at least 10 tools we can see from public records, including 6sense for sales, Google Analytics for analytics, Cloudflare for content delivery and Let's Encrypt for security. Last checked .
“SourceForge is the world's best and largest B2B software review and comparison platform with over 20 million visitors per month. SourceForge provides in-depth user reviews and a powerful business software comparison engine to help users find the right software for their needs. SourceForge also offer”
- Based in
- San Diego, United States
- Founded
- 2011
- Company page
- Tools found
- 10
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
SourceForge'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
1 tool, where the bytes are served from
CDN & Edge
Application
2 tools, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Sales & CRM
Company Ops
4 tools, what the team runs on day to day
Security & Compliance
SourceForge tech stack FAQ
What tools does SourceForge use?
We've found 10 tools at SourceForge (sf.net). Edge & Hosting: Cloudflare. Application: YouTube. Data & Observability: Google Analytics. Go-to-market: 6sense. Company Ops: Let's Encrypt, DigiCert and dmarcian. Last checked October 2, 2026.
What CRM does SourceForge use?
SourceForge uses 6sense for sales and CRM. We found 6sense through website code.
What analytics tools does SourceForge use?
SourceForge uses Google Analytics for analytics. We found Google Analytics through website code.
Does SourceForge use Cloudflare?
Yes. We found Cloudflare at SourceForge through custom domain. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what SourceForge uses?
We read public traces only: SourceForge'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.