Gitwork's tech stack
What does Gitwork use?
Gitwork (gitwork.co.uk) uses at least 11 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and LinkedIn for marketing. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Manchester, United Kingdom
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Gitwork'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
Application
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Company Ops
3 tools, what the team runs on day to day
Gitwork tech stack FAQ
What tools does Gitwork use?
We've found 11 tools at Gitwork (gitwork.co.uk). Edge & Hosting: Google Cloud and Netlify. Application: Google Fonts, Anthropic and Supabase. Data & Observability: Google Analytics. Go-to-market: LinkedIn. Company Ops: Google Workspace, SendGrid and Atlassian. Last checked October 6, 2026.
What cloud does Gitwork run on?
Gitwork uses Google Cloud and Netlify for hosting. We found Google Cloud through DNS records.
What email provider does Gitwork use?
Gitwork uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Gitwork use?
Gitwork uses Google Analytics for analytics. We found Google Analytics through website code.
What marketing software does Gitwork use?
Gitwork uses LinkedIn for marketing. We found LinkedIn through DNS verification records.
Does Gitwork use Google Analytics?
Yes. We found Google Analytics at Gitwork through website code. Google Analytics is used by 557,714 companies we track.
How does runsonwhat know what Gitwork uses?
We read public traces only: Gitwork'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.