runsonwhat

Jerry's tech stack

What does Jerry use?

Jerry (jerry.ai) uses at least 19 tools we can see from public records, including GitHub Pages for hosting, Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

“Jerry is building the AI agent to manage all your physical assets.”

Industry
Insurance
Size
201–1,000 employees
Based in
San Francisco, United States
Tools found
19
Categories
12
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

7 tools, what the team runs on day to day

Jerry tech stack FAQ

What tools does Jerry use?

We've found 19 tools at Jerry (jerry.ai). Edge & Hosting: Amazon Route 53, Amazon CloudFront and GitHub Pages. Application: Tailwind CSS. Data & Observability: Google Analytics, Hotjar and GrowthBook. Go-to-market: Meta Pixel, WordPress and Microsoft Ads. Company Ops: Google Workspace, SendGrid and Let's Encrypt. Last checked October 2, 2026.

What cloud does Jerry run on?

Jerry uses GitHub Pages for hosting. We found GitHub Pages through custom domain.

What email provider does Jerry use?

Jerry uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Jerry use?

Jerry uses Google Analytics and Hotjar for analytics. We found Google Analytics through website code.

What CMS does Jerry use?

Jerry uses WordPress for its website. We found WordPress through website code.

Does Jerry use Google Workspace?

Yes. We found Google Workspace at Jerry through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Jerry uses?

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