Cultured Code's tech stack
What does Cultured Code use?
Cultured Code (culturedcode.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Matomo for analytics and Amazon CloudFront for content delivery. Last checked .
- Size
- 1–10 employees
- Based in
- Germany
- Founded
- 2004
- Company page
- Tools found
- 10
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Cultured Code'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
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Cultured Code tech stack FAQ
What tools does Cultured Code use?
We've found 10 tools at Cultured Code (culturedcode.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: jQuery. Data & Observability: Matomo. Company Ops: Google Workspace, Apple Business and Amazon SES. Last checked October 3, 2026.
What cloud does Cultured Code run on?
Cultured Code uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Cultured Code use?
Cultured Code uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records and website code.
What analytics tools does Cultured Code use?
Cultured Code uses Matomo for analytics. We found Matomo through website code.
Does Cultured Code use jQuery?
Yes. We found jQuery at Cultured Code through website code. jQuery is used by 493,582 companies we track.
How does runsonwhat know what Cultured Code uses?
We read public traces only: Cultured Code'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.