runsonwhat

Petersen Automotive Museum's tech stack

What does Petersen Automotive Museum use?

Petersen Automotive Museum (petersen.org) uses at least 24 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Recharge for payments. Last checked .

Industry
Museums and Institutions
Size
51–200 employees
Based in
United States
Founded
1994
LinkedIn
Company page
Tools found
24
Categories
14
Layers
5 of 5
Last checked
Oct 2026

Petersen Automotive Museum'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

Application

7 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Petersen Automotive Museum tech stack FAQ

What tools does Petersen Automotive Museum use?

As of October 2026, runsonwhat has found 24 tools at Petersen Automotive Museum (petersen.org) in public records. Edge & Hosting: Cloudflare and Amazon Web Services. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Google Ads, Meta Pixel and Mailchimp. Company Ops: Google Workspace, SendGrid and Mailchimp Transactional. Last checked October 7, 2026.

What cloud does Petersen Automotive Museum run on?

Petersen Automotive Museum uses Amazon Web Services for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through Amazon Web Services code on petersen.org. Amazon Web Services is used by 144,602 companies runsonwhat tracks.

What email provider does Petersen Automotive Museum use?

Petersen Automotive Museum uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 395,458 companies runsonwhat tracks.

What payment provider does Petersen Automotive Museum use?

Petersen Automotive Museum uses Recharge for payments and billing, according to runsonwhat (October 2026). runsonwhat found Recharge through Recharge code on petersen.org. Recharge is used by 1,667 companies runsonwhat tracks.

What analytics tools does Petersen Automotive Museum use?

Petersen Automotive Museum uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on petersen.org. Google Analytics is used by 847,627 companies runsonwhat tracks.

What is Petersen Automotive Museum's website built with?

Petersen Automotive Museum uses Shopify for its website, alongside PageFly, according to runsonwhat (October 2026). runsonwhat found Shopify through a subdomain that points at Shopify and email records. Shopify is used by 58,538 companies runsonwhat tracks.

Does Petersen Automotive Museum use jQuery?

Yes. runsonwhat found jQuery at Petersen Automotive Museum through jQuery code on petersen.org. jQuery is a Frontend tool used by 894,059 companies runsonwhat tracks.

Which companies have a tech stack similar to Petersen Automotive Museum's?

The companies with the stacks most like Petersen Automotive Museum's are Kara Vita, Wet Noses, Fleshlight and Nourished, according to runsonwhat (October 2026). Each shares 14 to 17 tools with Petersen Automotive Museum, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Petersen Automotive Museum uses?

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