emmy's tech stack
What does emmy use?
emmy (emmy-sharing.de) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Internet
- Size
- 51–200 employees
- Based in
- Berlin, Germany
- Founded
- 2015
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
emmy'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.
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
emmy tech stack FAQ
What tools does emmy use?
We've found 12 tools at emmy (emmy-sharing.de). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and AppsFlyer. Go-to-market: Google Ads, WordPress and Zendesk. Company Ops: Microsoft 365 and Apple Business. Last checked October 4, 2026.
What email provider does emmy use?
emmy uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.
What does emmy use for customer support?
emmy uses Zendesk for customer support. We found Zendesk through email records and custom domain.
What analytics tools does emmy use?
emmy uses Google Analytics, Google Tag Manager and AppsFlyer for analytics. We found Google Analytics through website code.
What CMS does emmy use?
emmy uses WordPress for its website. We found WordPress through website code.
Does emmy use Microsoft 365?
Yes. We found Microsoft 365 at emmy through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what emmy uses?
We read public traces only: emmy'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.