DeepQ.com's tech stack
What does DeepQ.com use?
DeepQ.com (deepq.com) uses at least 13 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, GitBook for customer support and Wix for its website. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- Taiwan
- Company page
- Tools found
- 13
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
DeepQ.com'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
3 tools, where the bytes are served from
Application
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
DeepQ.com tech stack FAQ
What tools does DeepQ.com use?
We've found 13 tools at DeepQ.com (deepq.com). Edge & Hosting: GoDaddy, Google Cloud and Fastly. Application: GSAP, React and Anthropic. Data & Observability: Sentry. Go-to-market: Wix and GitBook. Company Ops: Microsoft 365 and SendGrid. Last checked October 7, 2026.
What cloud does DeepQ.com run on?
DeepQ.com uses Google Cloud for hosting. We found Google Cloud through website code.
What email provider does DeepQ.com use?
DeepQ.com uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What does DeepQ.com use for customer support?
DeepQ.com uses GitBook for customer support. We found GitBook through custom domain.
What CMS does DeepQ.com use?
DeepQ.com uses Wix for its website. We found Wix through custom domain, DNS records and website code.
Does DeepQ.com use Microsoft 365?
Yes. We found Microsoft 365 at DeepQ.com through email records and website code. Microsoft 365 is used by 685,859 companies we track.
How does runsonwhat know what DeepQ.com uses?
We read public traces only: DeepQ.com'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.