runsonwhat

222's tech stack

What does 222 use?

222 (222.place) uses at least 17 tools we can see from public records, including Netlify for hosting, Google Workspace for email and documents, Google Analytics for analytics and Mailchimp for marketing. Last checked .

“the AI social facilitator for offline human to human interactions”

Industry
Consumer
Size
11–50 employees
Based in
New York City, United States
Tools found
17
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

Application

2 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

222 tech stack FAQ

What tools does 222 use?

We've found 17 tools at 222 (222.place). Edge & Hosting: NS1, Netlify and Railway. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and web-vitals. Go-to-market: Meta Pixel, Google Ads and Mailchimp. Company Ops: Google Workspace, SendGrid and Resend. Last checked October 2, 2026.

What cloud does 222 run on?

222 uses Netlify and Railway for hosting. We found Netlify through website code.

What email provider does 222 use?

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

What analytics tools does 222 use?

222 uses Google Analytics, Google Tag Manager and PostHog for analytics. We found Google Analytics through website code.

What marketing software does 222 use?

222 uses Mailchimp for marketing. We found Mailchimp through email records.

Does 222 use Google Workspace?

Yes. We found Google Workspace at 222 through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what 222 uses?

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