Waterloo Records's tech stack
What does Waterloo Records use?
Waterloo Records (waterloorecords.com) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Shopify for its website, Klaviyo for marketing and Cloudflare for content delivery. Last checked .
- Industry
- Music
- Size
- 51–200 employees
- Based in
- Austin, United States
- Founded
- 1982
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Waterloo Records'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
CDN & Edge
Application
1 tool, what the product is built with
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Waterloo Records tech stack FAQ
What tools does Waterloo Records use?
We've found 8 tools at Waterloo Records (waterloorecords.com). Edge & Hosting: Cloudflare and Amazon Route 53. Go-to-market: Shopify and Klaviyo. Company Ops: Google Workspace and Amazon SES. Last checked October 3, 2026.
What email provider does Waterloo Records use?
Waterloo Records uses Google Workspace for email and documents. We found Google Workspace through email records.
What CMS does Waterloo Records use?
Waterloo Records uses Shopify for its website. We found Shopify through custom domain, DNS records and website code.
What marketing software does Waterloo Records use?
Waterloo Records uses Klaviyo for marketing. We found Klaviyo through DNS verification records.
Does Waterloo Records use Cloudflare?
Yes. We found Cloudflare at Waterloo Records through website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Waterloo Records uses?
We read public traces only: Waterloo Records'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.