CodeYam's tech stack
What does CodeYam use?
CodeYam (codeyam.com) uses at least 13 tools we can see from public records, including Render for hosting, Google Workspace for email and documents, Discord for customer support and PostHog for analytics. Last checked .
- Tools found
- 13
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
CodeYam'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
3 tools, where the bytes are served from
Application
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Workspace
People & HR
CodeYam tech stack FAQ
What tools does CodeYam use?
We've found 13 tools at CodeYam (codeyam.com). Edge & Hosting: Cloudflare, Namecheap and Render. Application: Google Fonts, Lottie and Supabase. Data & Observability: PostHog. Go-to-market: Discord and Substack. Company Ops: Google Workspace and Rippling. Last checked October 2, 2026.
What cloud does CodeYam run on?
CodeYam uses Render for hosting. We found Render through custom domain and website code.
What email provider does CodeYam use?
CodeYam uses Google Workspace for email and documents. We found Google Workspace through email records.
What does CodeYam use for customer support?
CodeYam uses Discord for customer support. We found Discord through website code.
What analytics tools does CodeYam use?
CodeYam uses PostHog for analytics. We found PostHog through website code.
What CMS does CodeYam use?
CodeYam uses Substack for its website. We found Substack through custom domain.
Does CodeYam use Cloudflare?
Yes. We found Cloudflare at CodeYam through website code. Cloudflare is used by 477,102 companies we track.
How does runsonwhat know what CodeYam uses?
We read public traces only: CodeYam'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.