TaxiGVA's tech stack
What does TaxiGVA use?
TaxiGVA (taxigva.ch) uses at least 12 tools we can see from public records, including Hostinger for hosting, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
“Service de taxi premium à Genève — Transfert aéroport, chauffeur privé, transport VIP”
- Industry
- Funeral
- Size
- 11–50 employees
- Based in
- Genève, Switzerland
- Founded
- 2010
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
TaxiGVA'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
Hosting & Cloud
CDN & Edge
Application
3 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Email Delivery
TaxiGVA tech stack FAQ
What tools does TaxiGVA use?
We've found 12 tools at TaxiGVA (taxigva.ch). Edge & Hosting: Cloudflare and Hostinger. Application: Google Fonts and Google Maps. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, WordPress and Yoast SEO. Company Ops: Resend. Last checked October 4, 2026.
What cloud does TaxiGVA run on?
TaxiGVA uses Hostinger for hosting. We found Hostinger through email records.
What analytics tools does TaxiGVA use?
TaxiGVA uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does TaxiGVA use?
TaxiGVA uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does TaxiGVA use Cloudflare?
Yes. We found Cloudflare at TaxiGVA through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what TaxiGVA uses?
We read public traces only: TaxiGVA'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.