runsonwhat

Shepherd's tech stack

What does Shepherd use?

Shepherd (shepherdinsurance.com) uses at least 15 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, PostHog for analytics and HubSpot CMS for its website. Last checked .

“Modernizing commercial insurance”

Industry
Insurance
Size
51–200 employees
Based in
San Francisco, United States
Tools found
15
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Shepherd tech stack FAQ

What tools does Shepherd use?

We've found 15 tools at Shepherd (shepherdinsurance.com). Edge & Hosting: Cloudflare and Vercel. Application: jQuery, Vimeo and OpenAI. Data & Observability: PostHog. Go-to-market: HubSpot CMS and Webflow. Company Ops: Google Workspace, Apple Business and Let's Encrypt. Last checked October 2, 2026.

What cloud does Shepherd run on?

Shepherd uses Vercel for hosting. We found Vercel through DNS records.

What email provider does Shepherd use?

Shepherd uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records.

What analytics tools does Shepherd use?

Shepherd uses PostHog for analytics. We found PostHog through website code.

What CMS does Shepherd use?

Shepherd uses HubSpot CMS and Webflow for its website. We found HubSpot CMS through custom domain.

Does Shepherd use Cloudflare?

Yes. We found Cloudflare at Shepherd through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Shepherd uses?

We read public traces only: Shepherd'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.