runsonwhat

Duke University's tech stack

What does Duke University use?

Duke University (goduke.com) uses at least 49 tools we can see from public records, including Amazon Web Services for hosting, Demandbase for sales, Google Analytics for analytics and Oracle Eloqua for marketing. Last checked .

Industry
Sports
Size
201–1,000 employees
Based in
Durham, United States
Founded
1838
LinkedIn
Company page
Tools found
49
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Duke University'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.

Duke University tech stack FAQ

What tools does Duke University use?

We've found 49 tools at Duke University (goduke.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: Google Fonts, Adobe Fonts and Vue.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Microsoft Ads and LinkedIn Insight Tag. Company Ops: reCAPTCHA, UserWay and Imperva. Last checked October 7, 2026.

What cloud does Duke University run on?

Duke University uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What CRM does Duke University use?

Duke University uses Demandbase for sales and CRM. We found Demandbase through website code.

What analytics tools does Duke University use?

Duke University uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What marketing software does Duke University use?

Duke University uses Oracle Eloqua for marketing. We found Oracle Eloqua through custom domain and website code.

Does Duke University use Cloudflare?

Yes. We found Cloudflare at Duke University through website code. Cloudflare is used by 568,709 companies we track.

How does runsonwhat know what Duke University uses?

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