runsonwhat

ChurchSource's tech stack

What does ChurchSource use?

ChurchSource (churchsource.com) uses at least 32 tools we can see from public records, including Microsoft 365 for email and documents, tawk.to for customer support, Google Analytics for analytics and PayPal for payments. Last checked .

Industry
Publishing
Size
201–1,000 employees
Based in
Grand Rapids, United States
Founded
1992
LinkedIn
Company page
Re-check liveVisit churchsource.com
Tools found
32
Categories
16
Layers
5 of 5
Last checked
Oct 2026

ChurchSource'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

7 tools, what the product is built with

Frontend

Auth & Identity

AI

Payments & Billing

Media & UI

Data & Observability

6 tools, what they measure and store

Monitoring

Analytics

Flags & Experiments

Go-to-market

13 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Support & Docs

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Workspace

Security & Compliance

Companies like ChurchSource also use

Tools common among companies with a similar stack that we haven't found at ChurchSource.

Companies with a stack like ChurchSource's

Ranked by shared tools, with rare tools counting more.

ChurchSource tech stack FAQ

What tools does ChurchSource use?

As of October 2026, runsonwhat has found 32 tools at ChurchSource (churchsource.com) in public records. Edge & Hosting: Cloudflare and Amazon CloudFront. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Datadog. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Company Ops: Microsoft 365, reCAPTCHA and SendGrid. Last checked October 8, 2026.

What email provider does ChurchSource use?

ChurchSource uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365 and email records. Microsoft 365 is used by 694,534 companies runsonwhat tracks.

What does ChurchSource use for customer support?

ChurchSource uses tawk.to for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found tawk.to through tawk.to code on churchsource.com. tawk.to is used by 15,255 companies runsonwhat tracks.

What payment provider does ChurchSource use?

ChurchSource uses PayPal for payments and billing, according to runsonwhat (October 2026). runsonwhat found PayPal through PayPal code on churchsource.com. PayPal is used by 33,373 companies runsonwhat tracks.

What analytics tools does ChurchSource use?

ChurchSource uses Google Analytics for analytics, alongside Google Tag Manager, Crazy Egg and Elevar, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on churchsource.com. Google Analytics is used by 812,490 companies runsonwhat tracks.

What is ChurchSource's website built with?

ChurchSource uses Shopify for its website, according to runsonwhat (October 2026). runsonwhat found Shopify through a subdomain that points at Shopify and DNS records. Shopify is used by 58,079 companies runsonwhat tracks.

Does ChurchSource use jQuery?

Yes. runsonwhat found jQuery at ChurchSource through jQuery code on churchsource.com. jQuery is a Frontend tool used by 858,270 companies runsonwhat tracks.

Which companies have a tech stack similar to ChurchSource's?

The companies with the stacks most like ChurchSource's are Anine Bing, ALEX AND ANI, MS NOW and Peet's Coffee, according to runsonwhat (October 2026). Each shares 13 to 20 tools with ChurchSource, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what ChurchSource uses?

runsonwhat reads public records only. Of the 32 tools at ChurchSource, 24 were found through code on churchsource.com, 3 through DNS records, 2 through email records, 2 through subdomains that point at the vendor and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and churchsource.com 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.