runsonwhat

StudyLingua's tech stack

What does StudyLingua use?

StudyLingua (studylingua.com) uses at least 13 tools we can see from public records, including Hostpoint for hosting, Microsoft 365 for email and documents, tawk.to for customer support and Seobility for marketing. Last checked .

Industry
Education Management
Size
51–200 employees
Based in
Sankt Gallen, Switzerland
LinkedIn
Company page
Tools found
13
Categories
8
Layers
4 of 5
Last checked
Oct 2026

StudyLingua'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

4 tools, what the product is built with

Go-to-market

3 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

StudyLingua tech stack FAQ

What tools does StudyLingua use?

We've found 13 tools at StudyLingua (studylingua.com). Edge & Hosting: Cloudflare and Hostpoint. Application: jQuery, Google Fonts and Google Maps. Go-to-market: tawk.to and Seobility. Company Ops: Microsoft 365, reCAPTCHA and Valimail. Last checked October 7, 2026.

What cloud does StudyLingua run on?

StudyLingua uses Hostpoint for hosting. We found Hostpoint through website code.

What email provider does StudyLingua use?

StudyLingua uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.

What does StudyLingua use for customer support?

StudyLingua uses tawk.to for customer support. We found tawk.to through website code.

What marketing software does StudyLingua use?

StudyLingua uses Seobility for marketing. We found Seobility through DNS verification records.

Does StudyLingua use Microsoft 365?

Yes. We found Microsoft 365 at StudyLingua through email records and website code. Microsoft 365 is used by 685,703 companies we track.

How does runsonwhat know what StudyLingua uses?

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