Gitstart Community's tech stack
What does Gitstart Community use?
Gitstart Community (gitstart.dev) uses at least 10 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Webflow for its website and Auth0 for sign-in. Last checked .
- Industry
- Software
- Size
- 51–200 employees
- Based in
- San Francisco, United States
- Founded
- 2019
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Gitstart Community'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
1 tool, what the product is built with
Auth & Identity
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
4 tools, what the team runs on day to day
Gitstart Community tech stack FAQ
What tools does Gitstart Community use?
We've found 10 tools at Gitstart Community (gitstart.dev). Edge & Hosting: Cloudflare, Vercel and Render. Application: Auth0. Go-to-market: Webflow. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 6, 2026.
What cloud does Gitstart Community run on?
Gitstart Community uses Vercel and Render for hosting. We found Vercel through custom domain and DNS verification records.
What email provider does Gitstart Community use?
Gitstart Community uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What CMS does Gitstart Community use?
Gitstart Community uses Webflow for its website. We found Webflow through custom domain.
Does Gitstart Community use Microsoft 365?
Yes. We found Microsoft 365 at Gitstart Community through DNS verification records. Microsoft 365 is used by 685,702 companies we track.
How does runsonwhat know what Gitstart Community uses?
We read public traces only: Gitstart Community'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.