# Bridge CDN > Bridge CDN is a content delivery network, currently in development, built so that > search crawlers and AI assistants are first-class visitors rather than an afterthought. Status: pre-launch. Bridge CDN has not launched and no launch date has been announced. Nothing described here has been measured in production. There is no published SLA, uptime figure, or edge-location count. ## Links - [Bridge CDN](https://bridge-cdn.com/): the pre-launch site — capabilities, Cloudflare migration notes, and FAQ. - [Waitlist](https://tally.so/r/GxDrGz): email-only signup, no payment details and no commitment. - [Sitemap](https://bridge-cdn.com/sitemap.xml): canonical URL list. ## What it is Bridge CDN is an edge delivery platform combining the layer you expect from a CDN — caching, DNS, TLS, and security — with delivery features aimed at indexing, answer engine optimization, and automated clients. ## Capabilities - Global CDN — caches your site close to the people requesting it, reducing origin load and round trips. - Instant DNS — authoritative DNS included rather than sold separately, with automatic DNSSEC signing. Record changes apply at the edge within seconds; resolver propagation still follows each record's TTL. - Instant SSL/TLS — per-hostname certificates issued and renewed automatically via ACME as part of adding a domain. Bringing your own certificate is not supported. - DDoS protection and WAF — a web application firewall filtering malicious requests at the edge, with three modes (off, monitor, block) so rules can be observed before they are enforced. There is deliberately no bot-fight switch. - Edge Workers — run custom logic at the edge to rewrite requests, adjust headers, or answer without touching origin. Included with paid domain plans rather than billed separately. - Origin Shield — keeps the origin address out of public DNS and absorbs repeat requests at the edge, so only genuine cache misses reach the origin. Enabled per hostname, default off; proxying applies to A and AAAA records. ## Compatibility Bridge CDN sits in front of any site, whether the origin answers over HTTPS or plain HTTP — no SDK, no plugin, no code changes. Onboarding is a nameserver switch, and a per-hostname proxy toggle keeps anything you'd rather not proxy on plain DNS. - SaaS and AI app builders — Shopify, Lovable, Base44, Bolt, v0, Replit, Webflow, Framer, Wix, Squarespace, BigCommerce, Ghost. Many hosted platforms already run behind a major CDN of their own, where stacking another proxy from the same network can conflict; Bridge CDN operates an independent edge, so it is designed to sit in front of them. - Cloud and serverless — Vercel, Netlify, AWS, Google Cloud, Azure, DigitalOcean, Render, Fly.io, Railway, Heroku. Bridge CDN fronts the URL the platform provides; build and deploy pipelines are untouched. - Self-hosted infrastructure — VPS, VDS, dedicated servers, bare metal, Docker, Kubernetes, on-prem, colocation. Anything with an IP address can serve as the origin. - Managed and shared hosting — WordPress hosts (WP Engine, Kinsta, SiteGround), cPanel and Plesk panels. The host stays the origin; Bridge CDN handles delivery, TLS, and crawler traffic in front. ## BotBridge BotBridge is a feature of Bridge CDN, not a separate product. It handles delivery to search crawlers and AI agents, serving rendered HTML to those clients so they index actual content instead of an empty JavaScript shell. Human visitors receive the normal site, unchanged. Bot classification is user-agent based and configurable per domain. It does not use IP reputation, reverse DNS, or fingerprinting. BotBridge has two parts. ### SEO, AEO & GEO optimization Search engine, answer engine, and generative engine optimization handled at the edge, rather than as a separate stack: - Better Core Web Vitals — edge caching reduces time to first byte and largest contentful paint for real visitors, which is what Core Web Vitals measure. - More crawl budget spent on real content — prerendering serves a rendered HTML snapshot to bots once warm, so crawlers are not waiting on JavaScript that never executes for them. The first request for an uncached URL is served from origin. - Faster indexation — IndexNow notifies participating search engines when a URL changes rather than waiting for the next crawl. On by default, with Bing and Yandex enabled; Seznam, Naver, and Yep are opt-in. Google does not participate in IndexNow. - Metadata gaps filled — missing descriptions, Open Graph, and structured data are generated for crawlers. It fills what is absent and does not overwrite existing tags. ### Bot and AI analytics Separate reporting on which crawlers and AI agents reach the site and what they request, across seven bot categories, the last of which is an unrecognized bucket. Crawl-infrastructure requests (robots.txt, sitemap, RSS) are counted apart from page views, and bot traffic is counted on its own plane so it cannot inflate human numbers. ## Migrating from Cloudflare Bridge CDN is positioned as a Cloudflare alternative for teams whose priority is search visibility and delivery to automated clients. It does not attempt to match Cloudflare's wider platform; teams depending on Zero Trust, R2, or Workers KV are better served there. You can connect a Cloudflare account over OAuth and import DNS records, page rules, and the zone SSL mode (which becomes per-hostname origin settings) instead of re-entering them by hand, then switch nameservers at your registrar. Two other import paths exist for non-Cloudflare incumbents: a public DNS scan, or a pasted zone file. Known limits, stated plainly: - Switching nameservers away from Cloudflare deactivates the zone there — expected as part of the move. If Cloudflare is the domain's registrar, the domain must be transferred out first, since Cloudflare Registrar requires Cloudflare nameservers. - Worker route patterns are imported; worker code is not and must be re-authored. - Only a subset of Cloudflare page-rule actions have equivalents; others do not carry over. - WAF rules, cache rulesets, and certificates are not importable. No claim is made that migration is instant, lossless, or zero-downtime. ## Who it is for - Ecommerce — large catalogues with crawl-coverage pressure and standing exposure to automated abuse. - Agencies — many client domains needing the same setup repeated cheaply. - Publishers — constant publishing where the gap between going live and being indexed matters. - Large websites — sites with 10,000 to 1,000,000+ pages, where prerendering and IndexNow direct crawl budget to content that matters instead of pages that never changed. ## Privacy Visitor analytics are measured at the edge with no client-side JavaScript and no cookies. Visitors are identified by a salted hash that rotates daily rather than by stored identifiers, and bot traffic is counted on a separate plane so it never inflates human numbers. ## Setup Bridge CDN sits in front of an existing site. No application code changes are required; setup is a nameserver change plus configuration in the dashboard. Your application, CMS, or site builder stays where it is.