Simpartout's tech stack
What does Simpartout use?
Simpartout (simpartout.fr) uses at least 8 tools we can see from public records, including Migadu for email and documents, Google Analytics for analytics, Amazon CloudFront for content delivery and Amazon SES for email delivery. Last checked .
“Simpartout propose des forfaits eSIM pour plus de 200 destinations dans le monde. Activation instantanée, sans changement de carte SIM.”
- Industry
- Telecommunications
- Based in
- Cambridge, United Kingdom
- Founded
- 2026
- Tools found
- 8
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Simpartout'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Simpartout tech stack FAQ
What tools does Simpartout use?
We've found 8 tools at Simpartout (simpartout.fr). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Next.js. Data & Observability: Google Analytics. Company Ops: Amazon SES and Migadu. Last checked October 4, 2026.
What email provider does Simpartout use?
Simpartout uses Migadu for email and documents. We found Migadu through email records.
What analytics tools does Simpartout use?
Simpartout uses Google Analytics for analytics. We found Google Analytics through website code.
Does Simpartout use Google Analytics?
Yes. We found Google Analytics at Simpartout through website code. Google Analytics is used by 304,093 companies we track.
How does runsonwhat know what Simpartout uses?
We read public traces only: Simpartout'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.