tzager's tech stack
What does tzager use?
tzager (intoolab.com) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Auth0 for sign-in. Last checked .
- Industry
- Internet
- Size
- 11–50 employees
- Based in
- London, United Kingdom
- Founded
- 2016
- Company page
- Tools found
- 13
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
tzager'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
Hosting & Cloud
CDN & Edge
Application
4 tools, what the product is built with
Frontend
Auth & Identity
Backend & Database
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
4 tools, what the team runs on day to day
Email Delivery
Collaboration
tzager tech stack FAQ
What tools does tzager use?
We've found 13 tools at tzager (intoolab.com). Edge & Hosting: Amazon Web Services, Amazon CloudFront and Fastly. Application: jQuery, Google Fonts and Firebase. Data & Observability: Google Analytics. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 6, 2026.
What cloud does tzager run on?
tzager uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does tzager use?
tzager uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does tzager use?
tzager uses Google Analytics for analytics. We found Google Analytics through website code.
Does tzager use Microsoft 365?
Yes. We found Microsoft 365 at tzager through DNS verification records. Microsoft 365 is used by 685,462 companies we track.
How does runsonwhat know what tzager uses?
We read public traces only: tzager'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.