Classical Comics's tech stack
What does Classical Comics use?
Classical Comics (classicalcomics.com) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Shopify for its website, Bugsnag for monitoring and Cloudflare for content delivery. Last checked .
- Industry
- Comics
- Size
- 1–10 employees
- Based in
- Birmingham, United Kingdom
- Founded
- 2006
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Classical Comics'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
CDN & Edge
Application
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Classical Comics tech stack FAQ
What tools does Classical Comics use?
We've found 9 tools at Classical Comics (classicalcomics.com). Edge & Hosting: Cloudflare. Application: Google Fonts, YouTube and Google Maps. Data & Observability: Bugsnag. Go-to-market: Shopify. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does Classical Comics use?
Classical Comics uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What CMS does Classical Comics use?
Classical Comics uses Shopify for its website. We found Shopify through custom domain, DNS records and website code.
Does Classical Comics use Microsoft 365?
Yes. We found Microsoft 365 at Classical Comics through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Classical Comics uses?
We read public traces only: Classical Comics'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.