The Infrastructure Behind Vibe-Coded Websites
Cloudflare and Vercel were the most frequent infrastructure detections across 780 VCL domains. The overlapping counts reveal more than a submitted URL alone.
A custom domain does not tell you which services run behind it. In VCL’s September snapshot, Cloudflare was detected on 302 custom domains and Vercel on 294, making them the two most frequent entries in the infrastructure table.
Both appeared in more than a third of successful lookups. Those shares can overlap: a website can use several infrastructure services, and a CDN detection does not necessarily identify its origin host.
What the provider could observe
DataForSEO technology lookups succeeded for 780 of the report’s 904 eligible unique custom domains. The table uses those 780 domains, including successful lookups with no detected technology.
| Detected service | Domains | Share of 780 successful lookups |
|---|---|---|
| Cloudflare | 302 | 38.7% |
| Vercel | 294 | 37.7% |
| Netlify | 52 | 6.7% |
| Amazon Web Services | 48 | 6.2% |
| jsDelivr | 21 | 2.7% |
| Google Cloud CDN | 20 | 2.6% |
| Amazon CloudFront | 19 | 2.4% |
| Amazon S3 | 12 | 1.5% |
The entries include hosting, content delivery and related infrastructure. Each name counts once per domain, and only detections appearing on at least five domains are shown. Broad provider names and individual services may occur together.
Why a URL breakdown gives a different answer
The report also counts submitted URLs ending in shared domains such as vercel.app. That is a different population and a different measurement. A site using its own domain disappears from the shared-address count, even if Vercel still serves it.
Consequently, these detections should not be added to the shared-URL counts to construct a provider league table. One counts unique custom domains; the other counts submitted project links.
This is an observed infrastructure footprint, not hosting market share or a recommendation about which provider performs best. The sample covers VCL listings, provider observations can predate collection, and services can be present without being detected. The published table does not connect a particular provider to higher traffic or better performance.
Data and source. State of Vibe Coding 2026, Dataset v7: detected infrastructure, cutoff September 11, 2026 at 09:40:56 UTC. See the edition’s methodology for domain deduplication and technology coverage.
The full State of Vibe Coding report keeps submitted addresses, detected infrastructure and measured page scores separate.