Coming soon
Fast for people. Readable for AI. Found by search.
Bridge CDN is a content delivery network being built so that search crawlers and AI assistants are first-class visitors, not an afterthought — alongside the DNS, TLS, and security layer you already expect from an edge platform.
Email only. The waitlist is how you hear first when access opens.
Bridge CDN has not launched yet. It is in active development, and the waitlist is open.
Join the waitlistCapabilities
The edge stack you expect.
Bridge CDN is designed as a complete edge platform, so moving to it does not mean giving up the pieces you already run.
-
Global CDN A content delivery network caches your site close to the people requesting it. Bridge CDN handles static and dynamic delivery from the edge, so requests are answered near the visitor and only genuine cache misses reach your origin.
-
Instant DNS Authoritative DNS is included rather than sold separately, with automatic DNSSEC signing. Record changes apply at the Bridge CDN edge within seconds; resolver-side propagation still follows each record's TTL.
-
Instant SSL/TLS Certificates are issued per hostname and renewed for you over ACME. HTTPS is part of adding a domain rather than a separate task you have to remember to repeat.
-
DDoS protection & WAF A web application firewall filters malicious requests at the edge before they reach your origin. Three modes — off, monitor, block — so you watch what the rules would do before enforcing them, plus per-domain rate limiting. There is deliberately no bot-fight switch to misconfigure.
-
Edge Workers Edge workers run your own logic at the edge — rewriting requests, adjusting headers, or answering outright without touching your origin. Included with paid domain plans, not a separate account or usage bill.
-
Origin Shield Origin shielding keeps your origin address out of public DNS and absorbs repeat requests at the edge, so only genuine cache misses reach your servers. Enabled per hostname, so you decide what is proxied.
Compatibility
Works in front of anything you run.
Bridge CDN sits in front of any site, whether your 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 & AI app builders Many hosted platforms already run behind a major CDN of their own — exactly 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 the sites and stores you build there.
-
Cloud & serverless Apps on managed clouds keep deploying exactly as they do today. Bridge CDN fronts the URL your platform gives you, adds caching and crawler delivery at the edge, and leaves your build and deploy pipeline alone.
-
Your own servers Anything with an IP address can sit behind Bridge CDN. Point DNS at your machines, proxy the hostnames you choose, and keep full control of the stack behind the edge.
-
Managed & shared hosting Classic hosting works unchanged: WordPress hosts, cPanel and Plesk panels, and managed platforms all serve as the origin while Bridge CDN handles delivery, TLS, and crawler traffic in front.
The difference
BotBridge — delivery for crawlers and AI agents.
Search crawlers and AI assistants do not browse the way people do. BotBridge bridges that gap for the era of the agentic web: AI agents and modern crawlers get fast, fully rendered HTML they can read outright, while human visitors get your normal site, unchanged.
SEO, AEO & GEO optimization
Search engine, answer engine, and generative engine optimization all come down to the same thing: making a site legible to machines that read it without executing it. BotBridge handles that at the edge — prerendering pages for crawlers, submitting changed URLs through IndexNow, and closing gaps in page metadata — so it is not a separate stack you maintain.
- Better Core Web Vitals Edge caching cuts time to first byte and largest contentful paint for real visitors — which is what Core Web Vitals actually measure.
- More crawl budget on real content Crawlers spend their budget reading pages instead of waiting on JavaScript that never renders for them.
- Faster indexation IndexNow tells participating search engines a URL changed, rather than leaving them to find it on the next crawl.
- Metadata gaps filled Missing descriptions, Open Graph, and structured data get generated for crawlers — filling what is absent, never overwriting tags you wrote.
Bot & AI analytics
Bot and AI analytics show the traffic ordinary analytics throws away. Most tools filter bots out or never see them at all, because agents do not run tracking scripts. Bridge CDN counts them at the edge: which search crawlers and AI agents visit, what they request, and how often — across seven bot categories, with robots.txt, sitemap, and RSS hits counted apart from page views.
That behavior is exactly what AEO and GEO turn on: you cannot improve how answer and generative engines read your site without seeing them read it. Measurement is cookie-free with no client-side script, and bot traffic stays on its own plane, so it never inflates your human numbers.
Cloudflare alternative
Bring your Cloudflare setup with you.
If you run Cloudflare today, the cost of trying something else is usually the rebuild — re-entering every DNS record and page rule by hand. Bridge CDN is designed to remove that step: connect your Cloudflare account over OAuth and import what you already configured, then switch nameservers once you have reviewed it. Not coming from Cloudflare? A public DNS scan or a pasted zone file work too.
- Connect Authorize Bridge CDN to read your Cloudflare account, read-only.
- Import Bring across DNS records, page rules, worker routes, and your SSL mode as per-hostname origin settings.
- Review Review your imported DNS records before they go live. Nothing changes until you say so.
- Switch Point your registrar's nameservers at Bridge CDN and let them propagate.
Worth knowing up front: switching nameservers away from Cloudflare deactivates the zone there — expected as part of the move. If Cloudflare is also your domain registrar, transfer the domain out first: Cloudflare Registrar requires Cloudflare nameservers.
Who it is for
Built for sites that live on search.
Ecommerce
Large catalogues put real pressure on crawl coverage, and storefronts are a standing target for automated abuse. Bridge CDN is built to address both at the same layer.
Agencies
Running many client domains means repeating the same setup over and over. Per-domain settings and Cloudflare import are meant to make that repetition cheap.
Publishers
When publishing is constant, the gap between going live and being indexed is the thing that hurts. IndexNow and prerendering are aimed squarely at that gap.
Large websites
10,000 pages? 100,000? A million and more? Bridge CDN is built with huge sites in mind: prerendering and IndexNow put your crawl budget where it counts, so search engines spend each visit on content that matters instead of re-fetching pages that never changed.
Questions
What people ask before joining.
What is Bridge CDN?
Bridge CDN is a content delivery network built so search crawlers and AI assistants are first-class visitors. It combines edge caching, DNS, TLS, and security with delivery features aimed at indexing and answer engines. It has not launched yet.
When does Bridge CDN launch?
No launch date has been announced. The service is in active development, and the waitlist is the way to hear when access opens.
Is Bridge CDN a Cloudflare alternative?
Yes — that is the intended positioning, for teams whose priority is search visibility and delivery to automated clients. Bridge CDN covers the familiar edge layer: CDN, DNS, TLS, DDoS protection, WAF, and edge workers. It does not try to match Cloudflare's wider platform, so if you depend on things like Zero Trust, R2, or Workers KV, Cloudflare remains the better fit.
Can I move my Cloudflare configuration across?
Yes. You connect your Cloudflare account and import DNS records, page rules, worker routes, and your SSL mode instead of re-entering them by hand, then switch nameservers at your registrar. Two caveats: worker code does not import and has to be re-authored, and if Cloudflare is your domain registrar you must transfer the domain out first, since Cloudflare Registrar requires Cloudflare nameservers.
Do I have to change my application code?
No. Bridge CDN sits in front of your existing site, so your application, CMS, or site builder stays where it is. Setup is a nameserver change plus configuration in the dashboard.
What is BotBridge?
BotBridge is the Bridge CDN feature that handles delivery to search crawlers and AI agents. It covers SEO, AEO, and GEO optimization — prerendering, IndexNow submission, and page metadata — plus separate bot and AI analytics. Crawlers get rendered HTML so they index your content rather than an empty JavaScript shell; human visitors get your normal site.
Does Bridge CDN need cookies or a tracking script for analytics?
No. Visitor analytics are measured at the edge with no client-side JavaScript and no cookies, and bot traffic is counted separately so it never inflates your human numbers. Visitors are identified by a salted hash that rotates daily rather than by stored identifiers.
What does joining the waitlist involve?
You leave your email on a short form. It is used to tell you when Bridge CDN opens up — there is no commitment and no payment details. Pricing has not been announced yet; in return for joining early you receive a 50% discount code for your first 12 months once Bridge CDN goes live.
Get early access
Be there when Bridge CDN opens.
The waitlist is how early access is handed out, and how you will hear about launch.
Email only. No payment details, and no commitment to buy anything.
Receive a 50% discount code for your first 12 months once Bridge CDN goes live!