runsonwhat

AutoSitu's tech stack

What does AutoSitu use?

AutoSitu (autositu.com) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, Microsoft Clarity for analytics, web-vitals for monitoring and Oneleet for security. Last checked .

“The AI operating system for the built world. Connected intelligence from feasibility to construction — site feasibility, design review & QA/QC, code compliance, quantity takeoff, and scope gap analysis in one system for municipalities, architects, and developers.”

Industry
Legal
Size
1–10 employees
Based in
Detroit, United States
Founded
2024
LinkedIn
Company page
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

1 tool, where the bytes are served from

Application

5 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

AutoSitu tech stack FAQ

What tools does AutoSitu use?

We've found 12 tools at AutoSitu (autositu.com). Edge & Hosting: Namecheap. Application: React, Tailwind CSS and Next.js. Data & Observability: Microsoft Clarity, web-vitals and PostHog. Company Ops: Google Workspace and Oneleet. Last checked October 2, 2026.

What email provider does AutoSitu use?

AutoSitu uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does AutoSitu use?

AutoSitu uses Microsoft Clarity and PostHog for analytics. We found Microsoft Clarity through website code.

Does AutoSitu use Google Workspace?

Yes. We found Google Workspace at AutoSitu through email records. Google Workspace is used by 384,320 companies we track.

How does runsonwhat know what AutoSitu uses?

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