Source Library's tech stack
What does Source Library use?
Source Library (sourcelibrary.org) uses at least 13 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Google Analytics for analytics and web-vitals for monitoring. Last checked .
“A digital library project of the Embassy of the Free Mind, continuing the mission of Cosimo de' Medici and Marsilio Ficino.”
- Tools found
- 13
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Source Library'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
Hosting & Cloud
CDN & Edge
Application
5 tools, what the product is built with
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Source Library tech stack FAQ
What tools does Source Library use?
We've found 13 tools at Source Library (sourcelibrary.org). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts, React and Tailwind CSS. Data & Observability: Google Analytics, web-vitals and PostHog. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.
What cloud does Source Library run on?
Source Library uses Vercel for hosting. We found Vercel through website code.
What email provider does Source Library use?
Source Library uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Source Library use?
Source Library uses Google Analytics and PostHog for analytics. We found Google Analytics through website code.
Does Source Library use Cloudflare?
Yes. We found Cloudflare at Source Library through DNS records and website code. Cloudflare is used by 470,350 companies we track.
How does runsonwhat know what Source Library uses?
We read public traces only: Source Library'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.