CodeCannon's tech stack
What does CodeCannon use?
CodeCannon (codecannon.dev) uses at least 11 tools we can see from public records, including DigitalOcean for hosting, Proton Mail for email and documents, Discord for customer support and PostHog for analytics. Last checked .
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
CodeCannon'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
Hosting & Cloud
Application
4 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
CodeCannon tech stack FAQ
What tools does CodeCannon use?
We've found 11 tools at CodeCannon (codecannon.dev). Edge & Hosting: DigitalOcean. Application: Google Fonts, Font Awesome and Vue.js. Data & Observability: web-vitals and PostHog. Go-to-market: Discord. Company Ops: Red Sift OnDMARC and Proton Mail. Last checked October 2, 2026.
What cloud does CodeCannon run on?
CodeCannon uses DigitalOcean for hosting. We found DigitalOcean through DNS records.
What email provider does CodeCannon use?
CodeCannon uses Proton Mail for email and documents. We found Proton Mail through DNS verification records and email records.
What does CodeCannon use for customer support?
CodeCannon uses Discord for customer support. We found Discord through website code.
What analytics tools does CodeCannon use?
CodeCannon uses PostHog for analytics. We found PostHog through website code.
Does CodeCannon use Google Fonts?
Yes. We found Google Fonts at CodeCannon through website code. Google Fonts is used by 315,791 companies we track.
How does runsonwhat know what CodeCannon uses?
We read public traces only: CodeCannon'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.