runsonwhat

Pizza King's tech stack

What does Pizza King use?

Pizza King (pizzaking.com) uses at least 8 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and reCAPTCHA for security. Last checked .

Industry
Restaurants
Size
201–1,000 employees
Based in
Muncie, United States
Founded
1958
LinkedIn
Company page
Tools found
8
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Pizza King'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

1 tool, where the bytes are served from

Hosting & Cloud

Application

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Pizza King tech stack FAQ

What tools does Pizza King use?

We've found 8 tools at Pizza King (pizzaking.com). Edge & Hosting: Google Cloud. Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: Simpli.fi. Company Ops: Google Workspace and reCAPTCHA. Last checked October 8, 2026.

What cloud does Pizza King run on?

Pizza King uses Google Cloud for hosting. We found Google Cloud through DNS records.

What email provider does Pizza King use?

Pizza King uses Google Workspace for email and documents. We found Google Workspace through email records and website code.

What analytics tools does Pizza King use?

Pizza King uses Google Analytics for analytics. We found Google Analytics through website code.

Does Pizza King use jQuery?

Yes. We found jQuery at Pizza King through website code. jQuery is used by 761,763 companies we track.

How does runsonwhat know what Pizza King uses?

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