runsonwhat

Imvu's tech stack

What does Imvu use?

Imvu (imvu.com) uses at least 29 tools we can see from public records, including WP Engine for hosting, Google Workspace for email and documents, Freshdesk for customer support and Google Analytics for analytics. Last checked .

Industry
Internet
Size
201–1,000 employees
Based in
Redwood City, United States
Founded
2004
LinkedIn
Company page
Tools found
29
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

Backend & Database

Media & UI

Data & Observability

2 tools, what they measure and store

Company Ops

7 tools, what the team runs on day to day

Imvu tech stack FAQ

What tools does Imvu use?

We've found 29 tools at Imvu (imvu.com). Edge & Hosting: WP Engine. Application: Lottie and MongoDB Atlas. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Pinterest. Company Ops: Google Workspace, Apple Business and Atlassian. Last checked October 3, 2026.

What cloud does Imvu run on?

Imvu uses WP Engine for hosting. We found WP Engine through custom domain.

What email provider does Imvu use?

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

What does Imvu use for customer support?

Imvu uses Freshdesk for customer support. We found Freshdesk through custom domain and email records.

What analytics tools does Imvu use?

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

Does Imvu use Google Workspace?

Yes. We found Google Workspace at Imvu through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Imvu uses?

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