AGENOLX's tech stack
What does AGENOLX use?
AGENOLX (testset.io) uses at least 9 tools we can see from public records, including Google Analytics for analytics, Magento for its website, Branch for marketing and New Relic for monitoring. Last checked .
“AGENOLX menghadirkan bonus new member 20% untuk deposit pertama serta cashback harian dengan sistem aman, akses cepat, dan pengalaman bermain online terpercaya.”
- Industry
- Online Media
- Size
- 51–200 employees
- Based in
- Houston, United States
- Founded
- 2024
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
AGENOLX'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
3 tools, what the product is built with
Search
Media & UI
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
AGENOLX tech stack FAQ
What tools does AGENOLX use?
We've found 9 tools at AGENOLX (testset.io). Edge & Hosting: Cloudflare. Application: Google Maps, ShareThis and Klevu. Data & Observability: Google Analytics and New Relic. Go-to-market: Magento and Branch. Last checked October 6, 2026.
What analytics tools does AGENOLX use?
AGENOLX uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does AGENOLX use?
AGENOLX uses Magento for its website. We found Magento through website code.
What marketing software does AGENOLX use?
AGENOLX uses Branch for marketing. We found Branch through website code.
Does AGENOLX use Cloudflare?
Yes. We found Cloudflare at AGENOLX through DNS records and website code. Cloudflare is used by 501,451 companies we track.
How does runsonwhat know what AGENOLX uses?
We read public traces only: AGENOLX'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.