Larach Y Cía's tech stack
What does Larach Y Cía use?
Larach Y Cía (larachycia.com) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Retail
- Size
- 1,001–5,000 employees
- Based in
- Honduras
- Founded
- 1962
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Larach Y Cía'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
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Support & Docs
Company Ops
1 tool, what the team runs on day to day
Workspace
Larach Y Cía tech stack FAQ
What tools does Larach Y Cía use?
We've found 8 tools at Larach Y Cía (larachycia.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: YouTube and Angular. Data & Observability: Google Analytics and Hotjar. Go-to-market: Zendesk. Company Ops: Google Workspace. Last checked October 3, 2026.
What email provider does Larach Y Cía use?
Larach Y Cía uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Larach Y Cía use for customer support?
Larach Y Cía uses Zendesk for customer support. We found Zendesk through website code.
What analytics tools does Larach Y Cía use?
Larach Y Cía uses Google Analytics and Hotjar for analytics. We found Google Analytics through website code.
Does Larach Y Cía use Google Workspace?
Yes. We found Google Workspace at Larach Y Cía through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Larach Y Cía uses?
We read public traces only: Larach Y Cía'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.