Tumbleweed's tech stack
What does Tumbleweed use?
Tumbleweed (tumbleweedrestaurants.com) uses at least 16 tools we can see from public records, including WP Engine for hosting, Google Analytics for analytics, PayPal for payments and WordPress for its website. Last checked .
- Tools found
- 16
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
Tumbleweed'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
CDN & Edge
Application
6 tools, what the product is built with
Frontend
Payments & Billing
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Tumbleweed tech stack FAQ
What tools does Tumbleweed use?
We've found 16 tools at Tumbleweed (tumbleweedrestaurants.com). Edge & Hosting: Cloudflare and WP Engine. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Last checked October 3, 2026.
What cloud does Tumbleweed run on?
Tumbleweed uses WP Engine for hosting. We found WP Engine through custom domain, DNS verification records and website code.
What payment provider does Tumbleweed use?
Tumbleweed uses PayPal for payments. We found PayPal through website code.
What analytics tools does Tumbleweed use?
Tumbleweed uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Tumbleweed use?
Tumbleweed uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.
Does Tumbleweed use Cloudflare?
Yes. We found Cloudflare at Tumbleweed through DNS records and website code. Cloudflare is used by 303,836 companies we track.
How does runsonwhat know what Tumbleweed uses?
We read public traces only: Tumbleweed'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.