Clarisync's tech stack
What does Clarisync use?
Clarisync (clarisync.com) uses at least 12 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Software
- Size
- 201–1,000 employees
- Based in
- London, United Kingdom
- Founded
- 2021
- Company page
- Tools found
- 12
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Clarisync'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
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
3 tools, what the team runs on day to day
Clarisync tech stack FAQ
What tools does Clarisync use?
We've found 12 tools at Clarisync (clarisync.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: GSAP, React and Tailwind CSS. Data & Observability: Google Analytics. Company Ops: Microsoft 365, reCAPTCHA and Amazon SES. Last checked October 7, 2026.
What cloud does Clarisync run on?
Clarisync uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Clarisync use?
Clarisync uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does Clarisync use?
Clarisync uses Google Analytics for analytics. We found Google Analytics through website code.
Does Clarisync use Google Analytics?
Yes. We found Google Analytics at Clarisync through website code. Google Analytics is used by 724,524 companies we track.
How does runsonwhat know what Clarisync uses?
We read public traces only: Clarisync'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.