Files.fm Cloud Storage's tech stack
What does Files.fm Cloud Storage use?
Files.fm Cloud Storage (files.fm) uses at least 17 tools we can see from public records, including Microsoft 365 for email and documents, Yandex Webmaster for marketing, Better Stack for monitoring and Cloudflare for content delivery. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- Riga, Latvia
- Founded
- 2008
- Company page
- Tools found
- 17
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Files.fm Cloud Storage'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
CDN & Edge
Application
2 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
10 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Files.fm Cloud Storage tech stack FAQ
What tools does Files.fm Cloud Storage use?
We've found 17 tools at Files.fm Cloud Storage (files.fm). Edge & Hosting: Cloudflare. Application: OpenAI. Data & Observability: Better Stack. Go-to-market: Yandex Webmaster, Google Ad Manager and Criteo. Company Ops: Microsoft 365, Detectify and Loader.io. Last checked October 4, 2026.
What email provider does Files.fm Cloud Storage use?
Files.fm Cloud Storage uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What marketing software does Files.fm Cloud Storage use?
Files.fm Cloud Storage uses Yandex Webmaster for marketing. We found Yandex Webmaster through DNS verification records.
Does Files.fm Cloud Storage use Microsoft 365?
Yes. We found Microsoft 365 at Files.fm Cloud Storage through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Files.fm Cloud Storage uses?
We read public traces only: Files.fm Cloud Storage'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.