CLOUDFLARE-NATIVE · BUSINESS CONTINUITY CLOUDFLARE 原生 · 业务连续性

Networks get blocked. Your service does not. 网络被封,业务不断。

Domain Shield is a Cloudflare-native edge service that keeps your web app reachable for real users when a primary entry domain becomes hard to reach. It runs inside your own Cloudflare account, activates automatically in the user's browser, and reroutes to a healthy backup — your team keeps shipping product. Domain Shield 是一套 Cloudflare 原生的边缘可用性服务,所有组件部署在您既有的 Cloudflare 账号内。当主入口域名出现可达性问题时,它在用户浏览器里自动检测并切换到健康的备用入口,业务无中断,研发团队继续专注产品本身。

No app rewrite 无需改源码 Autonomous handover, zero ops involvement 自动切换 · 无需运维介入 Recovery in seconds 秒级恢复

Why teams choose us 为什么选择我们

When an entry domain becomes hard to reach for some users, the cost shows up immediately: lost sessions, lost revenue, support floods. Domain Shield turns that into a non-event. 当某个入口域名对部分用户变得难以访问,代价立刻体现:会话断掉、营收掉、客服爆。Domain Shield 把这件事变成「无事发生」。

Continuity, not contingency 连续,而不是应急

Users stay on the app. No manual notice, no chasing users with new links. 用户留在产品里。不用群发新地址、不用客服一个个对接。

Zero application changes 业务代码零改动

Pure edge layer. Your origin, your auth, your stack — untouched. 纯边缘层。源站、登录态、技术栈都不动。

Fast where it matters 该快的地方很快

Detection and switch happen in the browser at the network edge — measured in seconds. 检测与切换发生在用户浏览器与边缘之间,秒级生效。

Two operating modes 两种工作模式

Both modes deliver the same in-browser handover to a healthy entry; the difference is what runs on the backup domains themselves. You can change later — same control plane. 两种模式在浏览器侧的自动切换行为完全一致,区别在于备用域名上运行什么。后续可以切换,控制面是同一套。

Lite · default Lite · 默认

Backup domains as plain reverse proxies 备用域名为纯反代

Backup domains carry no edge code — they're plain reverse proxies to your origin. Lowest cost and the simplest posture. Backups only receive traffic when a failover actually happens. 备用域名不部署任何边缘代码,只是到您源站的普通反代。成本最低、姿态最轻。备用域名只在真正发生切换时才承接流量。

  • Lowest edge cost — backups charged only on failover 边缘成本最低 —— 备用只在切换时才计费
  • Backup domains stay under your direct DNS control 备用域名完全在您 DNS 直接管理下
  • Right choice for most consumer-facing deployments 大多数面向消费者的部署首选
Standard Standard

Backup domains as full nodes 备用域名同为完整节点

Backup domains run the same edge component as your primary. They can self-update, receive emergency directives, and be observed by the operations dashboard. Best when you need centralized control over the entire domain group. 备用域名部署与主域名相同的边缘组件,可以自主更新、接收紧急指令、在管理面板中被持续观测。适合需要对整个域名组统一管控的场景。

  • Uniform observability across every domain 整个域名组统一可观测
  • Emergency directives reach every domain 紧急指令能到达每个域名
  • Higher edge footprint on backup domains 备用域名的边缘占用略高

Built for teams who can't afford a quiet outage 为「悄悄掉量」零容忍的团队设计

If a portion of your users suddenly can't reach your entry domain, the metrics often look like a soft churn problem — but it's a reachability problem. We close that gap. 当一部分用户突然访问不到入口域名,看数据像是「自然流失」,其实是可达性问题。我们补上这一层。

Consumer brand applications 面向消费者的品牌应用

Anywhere the brand URL is itself a user-facing asset — a dropped session is a paying user gone, and the URL cannot easily be replaced. 品牌域名本身就是用户资产的场景:会话掉一次,付费用户就走一个,而 URL 难以随意替换。

Cross-region SaaS 跨地区 SaaS

Users in different regions hit different network conditions. Keep them all online. 不同地区用户网络环境差异大,让他们始终能用上服务。

High-stakes transactional flows 关键事务型流程

Checkout, sign-in, real-time sessions — places where a half-loaded page is worse than slow. 结算、登录、实时会话:页面半死不活比慢更糟。

Common questions 常见问题

Do we have to rewrite our app? 需要重写业务代码吗?

No. We sit at the edge and in the browser. Your application code, origin and auth stay exactly as they are. 不需要。我们只在边缘和浏览器层。业务代码、源站、登录态都不动。

How fast does it switch? 切换有多快?

Single-digit seconds in typical conditions, often under 10 seconds end-to-end. 典型条件下个位数秒级,端到端通常在 10 秒内完成。

Is this just a CDN? 这不就是个 CDN?

No. A CDN serves your origin from many edges, but it still resolves through the same entry domain. Domain Shield is about what happens when that entry itself becomes unreachable for some users. 不是。CDN 解决的是源站性能;它仍走同一个入口域名。Domain Shield 解决的是「这个入口本身对一部分用户访问不到」时该怎么办。

What does pricing look like? 怎么定价?

Per-tenant subscription with usage-based edge charges. We tailor it to your traffic profile after a short discovery call. 按租户订阅 + 按用量计费;我们简短沟通后会给你贴合实际流量的方案。

Get in touch 联系我们

Leave an email or any contact you prefer. We reply within one business day with a short discovery call slot. 留下邮箱或你常用的联系方式即可。我们一个工作日内回复,并约一个简短的沟通。