runsonwhat

Creek.org's tech stack

What does Creek.org use?

Creek.org (creek.fm) uses at least 7 tools we can see from public records, including Google Workspace for email and documents, StatCounter for analytics, Cloudflare for content delivery and SendGrid for email delivery. Last checked .

Industry
Software
Size
10,000+ employees
Based in
Johns Creek, United States
LinkedIn
Company page
Re-check liveVisit creek.fm
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Creek.org'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

3 tools, what the product is built with

Frontend

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Creek.org also use

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

Companies with a stack like Creek.org's

Ranked by shared tools, with rare tools counting more.

More Software companies

Other Software companies we've checked.

Creek.org tech stack FAQ

What tools does Creek.org use?

We've found 7 tools at Creek.org (creek.fm). Edge & Hosting: Cloudflare. Application: Adobe Fonts, Vue.js and Nuxt. Data & Observability: StatCounter. Company Ops: Google Workspace and SendGrid. Last checked October 3, 2026.

What email provider does Creek.org use?

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

What analytics tools does Creek.org use?

Creek.org uses StatCounter for analytics. We found StatCounter through website code.

Does Creek.org use Cloudflare?

Yes. We found Cloudflare at Creek.org through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Creek.org uses?

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