Radio Lazer's tech stack
What does Radio Lazer use?
Radio Lazer (radiolazer.com) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, WhatsApp Business for customer support, WordPress for its website and Cookiebot for security. Last checked .
- Industry
- Radio
- Size
- 51–200 employees
- Based in
- Oxnard, United States
- Founded
- 1991
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Radio Lazer'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
Application
6 tools, what the product is built with
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Radio Lazer tech stack FAQ
What tools does Radio Lazer use?
We've found 12 tools at Radio Lazer (radiolazer.com). Edge & Hosting: GoDaddy. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress and WhatsApp Business. Company Ops: Google Workspace and Cookiebot. Last checked October 3, 2026.
What email provider does Radio Lazer use?
Radio Lazer uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Radio Lazer use for customer support?
Radio Lazer uses WhatsApp Business for customer support. We found WhatsApp Business through website code.
What CMS does Radio Lazer use?
Radio Lazer uses WordPress for its website. We found WordPress through website code.
Does Radio Lazer use Google Workspace?
Yes. We found Google Workspace at Radio Lazer through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Radio Lazer uses?
We read public traces only: Radio Lazer'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.