Limobike's tech stack
What does Limobike use?
Limobike (virginlimobike.com) uses at least 12 tools we can see from public records, including Kinsta for hosting, WhatsApp Business for customer support, Google Tag Manager for analytics and WordPress for its website. Last checked .
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Limobike'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
4 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Limobike tech stack FAQ
What tools does Limobike use?
We've found 12 tools at Limobike (virginlimobike.com). Edge & Hosting: Cloudflare and Kinsta. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Tag Manager. Go-to-market: WordPress, Yoast SEO and WhatsApp Business. Company Ops: reCAPTCHA and Symantec Email Security.cloud. Last checked October 3, 2026.
What cloud does Limobike run on?
Limobike uses Kinsta for hosting. We found Kinsta through website code.
What does Limobike use for customer support?
Limobike uses WhatsApp Business for customer support. We found WhatsApp Business through website code.
What analytics tools does Limobike use?
Limobike uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
What CMS does Limobike use?
Limobike uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Limobike use Cloudflare?
Yes. We found Cloudflare at Limobike through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Limobike uses?
We read public traces only: Limobike'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.