runsonwhat

Fiorgo OÜ's tech stack

What does Fiorgo OÜ use?

Fiorgo OÜ (fiorgo.com) uses at least 7 tools we can see from public records, including DigitalOcean for hosting, Zoho for sales, Resend for email delivery and Let's Encrypt for security. Last checked .

“Fiorgo helps fashion and textile brands prepare product data for the EU Digital Product Passport.”

Based in
Sillamäe, Estonia
Founded
2012
LinkedIn
Company page
Re-check liveVisit fiorgo.com
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Fiorgo OÜ'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

AI

Go-to-market

2 tools, how they find and keep customers

Marketing

Sales & CRM

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Companies like Fiorgo OÜ also use

Tools common among companies with a similar stack that we haven't found at Fiorgo OÜ.

Companies with a stack like Fiorgo OÜ's

Ranked by shared tools, with rare tools counting more.

Fiorgo OÜ tech stack FAQ

What tools does Fiorgo OÜ use?

We've found 7 tools at Fiorgo OÜ (fiorgo.com). Edge & Hosting: DigitalOcean. Go-to-market: Zoho. Company Ops: Let's Encrypt, Sectigo and Resend. Last checked October 4, 2026.

What cloud does Fiorgo OÜ run on?

Fiorgo OÜ uses DigitalOcean for hosting. We found DigitalOcean through DNS records.

What CRM does Fiorgo OÜ use?

Fiorgo OÜ uses Zoho for sales and CRM. We found Zoho through DNS verification records and email records.

Does Fiorgo OÜ use Let's Encrypt?

Yes. We found Let's Encrypt at Fiorgo OÜ through DNS records. Let's Encrypt is used by 23,019 companies we track.

How does runsonwhat know what Fiorgo OÜ uses?

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