runsonwhat

ThinkingScript's tech stack

What does ThinkingScript use?

ThinkingScript (thinkingscript.com) uses at least 6 tools we can see from public records, including Fly.io for hosting, Google Workspace for email and documents and Plausible for analytics. Last checked .

Re-check liveVisit thinkingscript.com
Tools found
6
Categories
6
Layers
5 of 5
Last checked
Oct 2026

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

DNS

Application

1 tool, what the product is built with

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

1 tool, what the team runs on day to day

Workspace

Companies like ThinkingScript also use

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

Companies with a stack like ThinkingScript's

Ranked by shared tools, with rare tools counting more.

ThinkingScript tech stack FAQ

What tools does ThinkingScript use?

We've found 6 tools at ThinkingScript (thinkingscript.com). Edge & Hosting: Namecheap and Fly.io. Application: Google Fonts. Data & Observability: Plausible. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does ThinkingScript run on?

ThinkingScript uses Fly.io for hosting. We found Fly.io through website code.

What email provider does ThinkingScript use?

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

What analytics tools does ThinkingScript use?

ThinkingScript uses Plausible for analytics. We found Plausible through website code.

Does ThinkingScript use Google Fonts?

Yes. We found Google Fonts at ThinkingScript through website code. Google Fonts is used by 501,581 companies we track.

How does runsonwhat know what ThinkingScript uses?

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