runsonwhat

Shuffle's tech stack

What does Shuffle use?

Shuffle (shuffle.dev) uses at least 14 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, PayPal for payments and Sentry for monitoring. Last checked .

“Shuffle is a visual editor for developers that helps create beautiful websites and templates faster with AI features and 13,400+ UI components.”

Industry
IT Services
Size
1–10 employees
Based in
Warsaw, Poland
LinkedIn
Company page
Tools found
14
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

5 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Shuffle tech stack FAQ

What tools does Shuffle use?

We've found 14 tools at Shuffle (shuffle.dev). Edge & Hosting: Cloudflare. Application: jQuery, Tailwind CSS and PayPal. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Google Ads, Meta Pixel and X Ads. Company Ops: Google Workspace. Last checked October 2, 2026.

What email provider does Shuffle use?

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

What payment provider does Shuffle use?

Shuffle uses PayPal and Stripe for payments. We found PayPal through website code.

What analytics tools does Shuffle use?

Shuffle uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Shuffle use jQuery?

Yes. We found jQuery at Shuffle through website code. jQuery is used by 603,142 companies we track.

How does runsonwhat know what Shuffle uses?

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