runsonwhat

Cloudinary's tech stack

What does Cloudinary use?

Cloudinary (cloudinary.com) uses at least 65 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Salesforce for sales and Zendesk for customer support. Last checked .

Based in
Israel
Founded
2011
LinkedIn
Company page
Tools found
65
Categories
21
Layers
5 of 5
Last checked
Oct 2026

Cloudinary'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.

Cloudinary tech stack FAQ

What tools does Cloudinary use?

We've found 65 tools at Cloudinary (cloudinary.com). Edge & Hosting: Cloudflare, Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Atlassian Statuspage. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace, SendGrid and Apple Business. Last checked October 2, 2026.

What cloud does Cloudinary run on?

Cloudinary uses Vercel, Google Cloud and Amazon Web Services for hosting. We found Vercel through DNS verification records.

What CRM does Cloudinary use?

Cloudinary uses Salesforce and Mixmax for sales and CRM. We found Salesforce through email records.

What email provider does Cloudinary use?

Cloudinary uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records.

What does Cloudinary use for customer support?

Cloudinary uses Zendesk and Intercom for customer support. We found Zendesk through custom domain, email records and subprocessor list.

What payment provider does Cloudinary use?

Cloudinary uses Recurly for payments. We found Recurly through subprocessor list.

Does Cloudinary use Cloudflare?

Yes. We found Cloudflare at Cloudinary through DNS records, custom domain and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Cloudinary uses?

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