runsonwhat

fruux GmbH's tech stack

What does fruux GmbH use?

fruux GmbH (fruux.com) uses at least 12 tools we can see from public records, including Heroku for hosting, Google Workspace for email and documents, Google Analytics for analytics and Stripe for payments. Last checked .

Based in
Germany
Founded
2010
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

fruux GmbH'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

2 tools, where the bytes are served from

Application

2 tools, what the product is built with

Payments & Billing

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

6 tools, what the team runs on day to day

fruux GmbH tech stack FAQ

What tools does fruux GmbH use?

We've found 12 tools at fruux GmbH (fruux.com). Edge & Hosting: Amazon Route 53 and Heroku. Application: Google Fonts and Stripe. Data & Observability: Google Analytics. Company Ops: Google Workspace, SendGrid and Amazon SES. Last checked October 4, 2026.

What cloud does fruux GmbH run on?

fruux GmbH uses Heroku for hosting. We found Heroku through custom domain.

What email provider does fruux GmbH use?

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

What payment provider does fruux GmbH use?

fruux GmbH uses Stripe for payments. We found Stripe through DNS verification records and website code.

What analytics tools does fruux GmbH use?

fruux GmbH uses Google Analytics for analytics. We found Google Analytics through website code.

Does fruux GmbH use Google Workspace?

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

How does runsonwhat know what fruux GmbH uses?

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