runsonwhat

Brilliant Maps's tech stack

What does Brilliant Maps use?

Brilliant Maps (brilliantmaps.com) uses at least 37 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, WordPress for its website and beehiiv for marketing. Last checked .

Based in
United Kingdom
Founded
2016
LinkedIn
Company page
Tools found
37
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Brilliant Maps'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.

Brilliant Maps tech stack FAQ

What tools does Brilliant Maps use?

We've found 37 tools at Brilliant Maps (brilliantmaps.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery, Google Fonts and React. Data & Observability: Google Analytics, Google Tag Manager and comScore. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: reCAPTCHA and HUMAN Security. Last checked October 4, 2026.

What cloud does Brilliant Maps run on?

Brilliant Maps uses Amazon Web Services and Kinsta for hosting. We found Amazon Web Services through website code.

What analytics tools does Brilliant Maps use?

Brilliant Maps uses Google Analytics, Google Tag Manager and comScore for analytics, among 4 tools in this category. We found Google Analytics through website code.

What CMS does Brilliant Maps use?

Brilliant Maps uses WordPress and Rank Math for its website. We found WordPress through website code.

What marketing software does Brilliant Maps use?

Brilliant Maps uses beehiiv for marketing. We found beehiiv through website code.

Does Brilliant Maps use Cloudflare?

Yes. We found Cloudflare at Brilliant Maps through DNS records and website code. Cloudflare is used by 307,584 companies we track.

How does runsonwhat know what Brilliant Maps uses?

We read public traces only: Brilliant Maps'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.