Divain Team SL's tech stack
What does Divain Team SL use?
Divain Team SL (divainteam.com) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Shopify for its website and web-vitals for monitoring. Last checked .
- Industry
- Perfumery
- Based in
- Spain
- Founded
- 2021
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Divain Team SL'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
1 tool, what the product is built with
Backend & Database
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Divain Team SL tech stack FAQ
What tools does Divain Team SL use?
We've found 10 tools at Divain Team SL (divainteam.com). Edge & Hosting: Cloudflare and Google Cloud. Application: Supabase. Data & Observability: web-vitals. Go-to-market: Shopify. Company Ops: Microsoft 365, Google Workspace and Mailchimp Transactional. Last checked October 4, 2026.
What cloud does Divain Team SL run on?
Divain Team SL uses Google Cloud for hosting. We found Google Cloud through DNS records.
What email provider does Divain Team SL use?
Divain Team SL uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What CMS does Divain Team SL use?
Divain Team SL uses Shopify for its website. We found Shopify through DNS verification records.
Does Divain Team SL use Microsoft 365?
Yes. We found Microsoft 365 at Divain Team SL through DNS verification records. Microsoft 365 is used by 347,126 companies we track.
How does runsonwhat know what Divain Team SL uses?
We read public traces only: Divain Team SL'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.