Brilliant Light Power's tech stack
What does Brilliant Light Power use?
Brilliant Light Power (brilliantlightpower.com) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, WordPress for its website, Cloudflare for content delivery and Mailgun for email delivery. Last checked .
- Industry
- Renewables & Environment
- Size
- 11–50 employees
- Based in
- Cranbury, United States
- Founded
- 1991
- Company page
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Brilliant Light Power'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
5 tools, what the product is built with
Go-to-market
1 tool, how they find and keep customers
Website & CMS
Company Ops
3 tools, what the team runs on day to day
Brilliant Light Power tech stack FAQ
What tools does Brilliant Light Power use?
We've found 10 tools at Brilliant Light Power (brilliantlightpower.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress. Company Ops: Microsoft 365, reCAPTCHA and Mailgun. Last checked October 2, 2026.
What email provider does Brilliant Light Power use?
Brilliant Light Power uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.
What CMS does Brilliant Light Power use?
Brilliant Light Power uses WordPress for its website. We found WordPress through website code.
Does Brilliant Light Power use Microsoft 365?
Yes. We found Microsoft 365 at Brilliant Light Power through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Brilliant Light Power uses?
We read public traces only: Brilliant Light Power'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.