JYP Entertainment's tech stack
What does JYP Entertainment use?
JYP Entertainment (jype.com) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Zendesk for customer support and Amazon CloudFront for content delivery. Last checked .
- Industry
- Music
- Size
- 201–1,000 employees
- Based in
- South Korea
- Founded
- 1996
- Company page
- Tools found
- 8
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
JYP Entertainment'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
2 tools, what the product is built with
Frontend
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
JYP Entertainment tech stack FAQ
What tools does JYP Entertainment use?
We've found 8 tools at JYP Entertainment (jype.com). Edge & Hosting: Amazon CloudFront and Amazon Web Services. Application: Anthropic and Next.js. Go-to-market: Zendesk. Company Ops: Google Workspace and SendGrid. Last checked October 4, 2026.
What cloud does JYP Entertainment run on?
JYP Entertainment uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does JYP Entertainment use?
JYP Entertainment uses Google Workspace for email and documents. We found Google Workspace through email records.
What does JYP Entertainment use for customer support?
JYP Entertainment uses Zendesk for customer support. We found Zendesk through email records.
Does JYP Entertainment use Google Workspace?
Yes. We found Google Workspace at JYP Entertainment through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what JYP Entertainment uses?
We read public traces only: JYP Entertainment'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.