Human In Street's tech stack
What does Human In Street use?
Human In Street (humaninstreets.com) uses at least 10 tools we can see from public records, including IONOS for hosting, Google Analytics for analytics, Yoast SEO for its website and Mailjet for email delivery. Last checked .
- Industry
- Marketing and Advertising
- Size
- 11–50 employees
- Based in
- Muret, France
- Founded
- 2019
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Human In Street'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
Hosting & Cloud
Application
1 tool, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Human In Street tech stack FAQ
What tools does Human In Street use?
We've found 10 tools at Human In Street (humaninstreets.com). Edge & Hosting: IONOS. Application: Vue.js. Data & Observability: Google Analytics, Google Tag Manager and Matomo. Go-to-market: Google Ads and Yoast SEO. Company Ops: Mailjet and Axeptio. Last checked October 6, 2026.
What cloud does Human In Street run on?
Human In Street uses IONOS for hosting. We found IONOS through email records.
What analytics tools does Human In Street use?
Human In Street uses Google Analytics, Google Tag Manager and Matomo for analytics. We found Google Analytics through website code.
What CMS does Human In Street use?
Human In Street uses Yoast SEO for its website. We found Yoast SEO through website code.
Does Human In Street use Google Analytics?
Yes. We found Google Analytics at Human In Street through website code. Google Analytics is used by 560,193 companies we track.
How does runsonwhat know what Human In Street uses?
We read public traces only: Human In Street'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.