Jcu Singapore Alumni Association's tech stack
What does Jcu Singapore Alumni Association use?
Jcu Singapore Alumni Association (jcusaa.com) uses at least 7 tools we can see from public records, including Vercel for hosting, Vercel Analytics for analytics, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .
- Industry
- Education Management
- Size
- 201–1,000 employees
- Based in
- Singapore, Singapore
- Founded
- 2015
- Company page
- Tools found
- 7
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Jcu Singapore Alumni Association'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
CDN & Edge
Application
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Company Ops
1 tool, what the team runs on day to day
Email Delivery
Jcu Singapore Alumni Association tech stack FAQ
What tools does Jcu Singapore Alumni Association use?
We've found 7 tools at Jcu Singapore Alumni Association (jcusaa.com). Edge & Hosting: Cloudflare and Vercel. Application: YouTube, Next.js and Supabase. Data & Observability: Vercel Analytics. Company Ops: Amazon SES. Last checked October 6, 2026.
What cloud does Jcu Singapore Alumni Association run on?
Jcu Singapore Alumni Association uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What analytics tools does Jcu Singapore Alumni Association use?
Jcu Singapore Alumni Association uses Vercel Analytics for analytics. We found Vercel Analytics through website code.
Does Jcu Singapore Alumni Association use Cloudflare?
Yes. We found Cloudflare at Jcu Singapore Alumni Association through DNS records. Cloudflare is used by 571,895 companies we track.
How does runsonwhat know what Jcu Singapore Alumni Association uses?
We read public traces only: Jcu Singapore Alumni Association'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.