CivFund's tech stack
What does CivFund use?
CivFund (civfund.org) uses at least 15 tools we can see from public records, including Vercel for hosting, Zoho for sales, Google Analytics for analytics and web-vitals for monitoring. Last checked .
- Industry
- Financial Services
- Size
- 10,000+ employees
- Based in
- London, United Kingdom
- Founded
- 2021
- Company page
- Tools found
- 15
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
CivFund'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Security & Compliance
CivFund tech stack FAQ
What tools does CivFund use?
We've found 15 tools at CivFund (civfund.org). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts, Next.js and Adobe Fonts. Data & Observability: Google Analytics, Google Tag Manager and web-vitals. Go-to-market: Meta Pixel and Zoho. Company Ops: Let's Encrypt, Sectigo and DigiCert. Last checked October 3, 2026.
What cloud does CivFund run on?
CivFund uses Vercel for hosting. We found Vercel through DNS verification records, custom domain and website code.
What CRM does CivFund use?
CivFund uses Zoho for sales and CRM. We found Zoho through DNS verification records.
What analytics tools does CivFund use?
CivFund uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does CivFund use Cloudflare?
Yes. We found Cloudflare at CivFund through email records and DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what CivFund uses?
We read public traces only: CivFund'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.