runsonwhat

GitComet's tech stack

What does GitComet use?

GitComet (gitcomet.dev) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Discord for customer support and Google Analytics for analytics. Last checked .

Tools found
9
Categories
7
Layers
5 of 5
Last checked
Oct 2026

GitComet'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

Application

1 tool, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

GitComet tech stack FAQ

What tools does GitComet use?

We've found 9 tools at GitComet (gitcomet.dev). Edge & Hosting: Amazon Web Services and Microsoft Azure. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Discord. Company Ops: Microsoft 365. Last checked October 2, 2026.

What cloud does GitComet run on?

GitComet uses Amazon Web Services and Microsoft Azure for hosting. We found Amazon Web Services through website code.

What email provider does GitComet use?

GitComet uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.

What does GitComet use for customer support?

GitComet uses Discord for customer support. We found Discord through website code.

What analytics tools does GitComet use?

GitComet uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does GitComet use Microsoft 365?

Yes. We found Microsoft 365 at GitComet through DNS verification records, email records and website code. Microsoft 365 is used by 685,690 companies we track.

How does runsonwhat know what GitComet uses?

We read public traces only: GitComet'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.