Hack@ucf's tech stack
What does Hack@ucf use?
Hack@ucf (hackucf.org) uses at least 14 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Discord for customer support and Stripe for payments. Last checked .
- Industry
- Computer & Network Security
- Size
- 11–50 employees
- Based in
- Orlando, United States
- Founded
- 2012
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
Hack@ucf'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
5 tools, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
5 tools, what the team runs on day to day
Workspace
Security & Compliance
Companies like Hack@ucf also use
Tools common among companies with a similar stack that we haven't found at Hack@ucf.
Companies with a stack like Hack@ucf's
Ranked by shared tools, with rare tools counting more.
Vexterra GroupComputer & Network Security · 11–50 people4in common
RythminnoIT Services · 11–50 people3in common
DropeeInternet · 11–50 people8in common
Big Fig MattressRetail · 11–50 people5in common
Game DeveloperOnline Media · 11–50 people5in common
Cakewalk Software ConsultancySoftware · 11–50 people6in common
SalesforceInternet · 11–50 people1in common
InleedInternet · 11–50 people2in common
Hack@ucf tech stack FAQ
What tools does Hack@ucf use?
As of October 2026, runsonwhat has found 14 tools at Hack@ucf (hackucf.org) in public records. Edge & Hosting: Cloudflare and Google Cloud. Application: React, Tailwind CSS and Anthropic. Go-to-market: Discord. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 23, 2026.
What cloud does Hack@ucf run on?
Hack@ucf uses Google Cloud for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Google Cloud through a subdomain that points at Google Cloud. Google Cloud is used by 76,331 companies runsonwhat tracks.
What email provider does Hack@ucf use?
Hack@ucf uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on hackucf.org. Google Workspace is used by 406,796 companies runsonwhat tracks.
What does Hack@ucf use for customer support?
Hack@ucf uses Discord for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Discord through Discord code on hackucf.org. Discord is used by 6,149 companies runsonwhat tracks.
What payment provider does Hack@ucf use?
Hack@ucf uses Stripe for payments and billing, according to runsonwhat (October 2026). runsonwhat found Stripe through a DNS verification record for Stripe and code on hackucf.org. Stripe is used by 29,683 companies runsonwhat tracks.
Does Hack@ucf use Cloudflare?
Yes. runsonwhat found Cloudflare at Hack@ucf through DNS records that point at Cloudflare and email records. Cloudflare is a CDN & Edge tool used by 710,831 companies runsonwhat tracks.
Does Hack@ucf use AI tools?
Yes. runsonwhat has found Anthropic at Hack@ucf; Anthropic, for example, through a DNS verification record for Anthropic. AI services called only from servers leave no public trace, so Hack@ucf may use more AI tools than these.
Which companies have a tech stack similar to Hack@ucf's?
The companies with the stacks most like Hack@ucf's are Vexterra Group, Rythminno, Dropee and Big Fig Mattress, according to runsonwhat (October 2026). Each shares 3 to 8 tools with Hack@ucf, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what Hack@ucf uses?
runsonwhat reads public records only. Of the 14 tools at Hack@ucf, 8 were found through DNS records, 4 through code on hackucf.org, 1 through email records and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and hackucf.org about 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.