Imaginarium's tech stack
What does Imaginarium use?
Imaginarium (imaginarium.com.br) uses at least 14 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Retail
- Based in
- São Paulo, Brazil
- Founded
- 1991
- Tools found
- 14
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Imaginarium'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
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Imaginarium tech stack FAQ
What tools does Imaginarium use?
We've found 14 tools at Imaginarium (imaginarium.com.br). Edge & Hosting: Amazon CloudFront and Google Cloud. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Google Workspace, SendGrid and Mailchimp Transactional. Last checked October 3, 2026.
What cloud does Imaginarium run on?
Imaginarium uses Google Cloud for hosting. We found Google Cloud through DNS records.
What email provider does Imaginarium use?
Imaginarium uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Imaginarium use?
Imaginarium uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Imaginarium use Google Workspace?
Yes. We found Google Workspace at Imaginarium through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Imaginarium uses?
We read public traces only: Imaginarium'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.