runsonwhat

SF Anytime's tech stack

What does SF Anytime use?

SF Anytime (sfanytime.com) uses at least 22 tools we can see from public records, including Heroku for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Sentry for monitoring. Last checked .

Size
1–10 employees
Based in
Stockholm, Sweden
Founded
2002
LinkedIn
Company page
Tools found
22
Categories
15
Layers
5 of 5
Last checked
Oct 2026

SF Anytime'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

Hosting & Cloud

Application

6 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

SF Anytime tech stack FAQ

What tools does SF Anytime use?

We've found 22 tools at SF Anytime (sfanytime.com). Edge & Hosting: Amazon CloudFront and Heroku. Application: Google Fonts, Anthropic and OpenAI. Data & Observability: Google Analytics and Sentry. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 3, 2026.

What cloud does SF Anytime run on?

SF Anytime uses Heroku for hosting. We found Heroku through custom domain and website code.

What email provider does SF Anytime use?

SF Anytime uses Microsoft 365 and Exclaimer for email and documents. We found Microsoft 365 through email records and DNS verification records.

What analytics tools does SF Anytime use?

SF Anytime uses Google Analytics for analytics. We found Google Analytics through website code.

Does SF Anytime use Microsoft 365?

Yes. We found Microsoft 365 at SF Anytime through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what SF Anytime uses?

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