跳至主要内容Skip to content
私有化部署 · 企业软件授权 · 主控与节点均运行在您的基础设施中 Self-hosted · licensed enterprise software · control plane and nodes run on your own infrastructure 系统架构Architecture FAQ
私有化部署 · 企业软件授权Self-hosted · licensed enterprise software

一整套 CDN 系统,
装在您自己的服务器上
A complete CDN system,
deployed on servers you own

FunCDN 是一套可私有化部署的自建 CDN 系统。内容分发、安全防护、高可用容灾和日志分析归拢在同一套系统里,由一个主控管理边缘节点、回源中继和源站。主控和节点都部署在您自己的服务器上,配置、日志和数据由您自己掌握。 FunCDN is a self-hosted CDN system you can deploy privately. Content delivery, security, high-availability failover and log analytics come together in one system, with a single control plane managing edge nodes, origin relays and origins. The control plane and the nodes run on your own servers, and you keep the configuration, the logs and the data.

数据保留在自有网络Data stays in your network 支持 HTTP/2 与 WebSocket 反向代理HTTP/2 & WebSocket reverse proxy ACME 证书自动签发与续期ACME certificates issued and renewed automatically
funcdn · 主控control plane 私有化self-hosted
基础功能
Core
域名管理Domains
源站池Origin pools
缓存策略Cache rules
安全策略Security policy
SSL 证书SSL certs
基础设施
Infra
边缘节点Edge nodes
回源中继Origin relays
高可用规则HA rules
请求链路Request route
用户User 边缘节点Edge 中继·可选Relay·opt 源站Origin
边缘处理At the edge
缓存Cache 安全防护Security TLS HTTP/2 WebSocket
配置通过 gRPC 实时下发至节点;与主控断连时,节点继续使用本地缓存配置提供服务 Config streams to nodes over gRPC. If a node loses that connection, it keeps serving from its locally cached config.
证书自动续期Certs auto-renew
ACME · Let's Encrypt / ZeroSSL
一套完整系统包含What a complete system includes
主控Control planeREST 与 gRPC 编排REST + gRPC orchestration 边缘节点Edge nodes反向代理 · 缓存 · 安全策略reverse proxy · cache · security 回源中继Origin relay按需部署的回源链路origin route, deployed when needed 日志分析Log analytics外置 ClickHouse(可选)external ClickHouse, optional cdn-agent签名升级与配置同步signed upgrades · config sync 授权服务License server签名授权 · 三种授权版本signed licenses · three editions
01 · 产品能力Capabilities

核心能力集中在一个主控里Core capabilities live in one control plane

站点接入、缓存与回源、安全防护、证书、日志分析、节点运维和开发者接口,都从主控配置。首页只列要点,逐项说明在产品能力页。Site onboarding, caching and origin pull, security, certificates, log analytics, node operations and developer APIs are all configured from the control plane. The homepage lists the highlights; the capabilities page covers each one in detail.

站点接入与缓存Delivery & caching

域名接入后,流量由源站池负载均衡,并配主动健康检查;缓存分内存和磁盘两级,一键刷新下发到节点。Once a domain is onboarded, traffic is load-balanced across the origin pool, with active health checks behind it. The cache has two tiers, memory and disk, and a one-click purge is pushed out to the nodes.

安全防护Security

WAF、IP 黑白名单、访问限速、CC 防护和 JS Challenge,策略统一下发到边缘,每个站点可以单独组合。WAF, IP allow and deny lists, rate limiting, CC defense and JS Challenge. Policies are pushed to the edge from one place, and each site can combine them differently.

证书与 DNSCertificates & DNS

证书可以手动上传,也可以走 ACME 自动签发和续期。另外支持 CNAME Target,以及多家 DNS 服务商的授权接入。Upload certificates manually, or let ACME issue and renew them automatically. There is also CNAME target support and credentials for multiple DNS providers.

日志分析Log analytics

访问、缓存、回源和高可用日志都有记录,另有探测和审计。做日志分析时,可以选择接入外置 ClickHouse。Logs cover access, cache, origin pull and high availability, with probing and audit alongside them. Log analytics can optionally connect to an external ClickHouse.

节点运维Node operations

cdn-agent 采用签名升级,配置实时下发,节点侧用本地缓存做容错。健康心跳、备份恢复和操作审计也一并提供。cdn-agent upgrades are signed, config is pushed live, and nodes fall back to their locally cached copy. Heartbeats, backup and restore, and an operation audit trail are provided as well.

开发者接口Developer interfaces

REST API 配 API Token,接口按 OpenAPI 3.0 规范描述。边缘规则、脚本模板和用户 Edge KV 也都支持。A REST API with API tokens, described by an OpenAPI 3.0 spec. Edge rules, script templates and user Edge KV are supported as well.

查看全部产品能力 →See all capabilities → 完整清单同样覆盖节点运维、日志分析和开发者接口The full list also covers node operations, log analytics and developer interfaces
02 · 系统架构Architecture

请求面、主控与数据面相互独立Request, control and data planes stay separate

主控负责编排和配置下发,业务请求由边缘节点自己承载。节点与主控暂时断连时,仍按本地缓存的配置继续服务;运行日志则单独汇入日志分析数据面。The control plane handles orchestration and config push, while edge nodes carry the request traffic themselves. If a node loses its connection to the control plane for a while, it keeps serving from the config it has cached locally. Operational logs take a separate path into the log analytics data plane.

主控:基于 REST 与 gRPC 进行编排和配置下发Control plane: orchestration and config push over REST + gRPC 请求面:节点断连时仍可基于本地缓存配置继续服务Request plane: nodes keep serving from local cached config when disconnected 数据面:日志可选汇入外置 ClickHouse,用于日志分析Data plane: logs can flow into an external ClickHouse for analytics
请求处理链路Request handling path 架构概览Overview
请求链路Request route
用户User 边缘节点Edge 中继·可选Relay·opt 源站Origin
主控 · 编排与配置下发Control · orchestrate 请求面 · 边缘节点承载业务流量Request · at the edge 数据面 · 日志与日志分析Data · analytics
配置通过 gRPC 实时下发至节点;与主控断连时,节点继续使用本地缓存配置提供服务 Config streams to nodes over gRPC. If a node loses that connection, it keeps serving from its locally cached config.
03 · 应用场景Use cases

同一套系统,几种不同的用法One system, several ways to use it

这三个是比较典型的场景,用的都是现有产品能力的组合。其余场景和对应的能力列在应用场景页。These three are representative, and each one is a combination of capabilities the product already has. The rest, along with the capabilities behind them, are on the use cases page.

SCN 01

自建 / 私有化 CDNSelf-hosted CDN

内容分发跑在自己的服务器和带宽上。主控和节点都在自有网络里,配置和日志不用出内网。Content delivery runs on your own servers and bandwidth. The control plane and the nodes both sit inside your network, so configuration and logs never have to leave it.

私有化部署Self-hosted数据留在内网Data in-network
SCN 03

多源站容灾Multi-origin resilience

源站池做负载均衡,同时用主动健康检查发现故障,再自动切到可用的源站。也可以部署回源中继,当作备用的回源链路。The origin pool load-balances traffic and uses active health checks to detect failures, then switches automatically to a healthy origin. An origin relay can also be deployed as a backup path to the origin.

源站池Origin pools故障切换Failover
SCN 05

页面级高可用Page-level high availability

关键站点可以挂高可用规则。主地址请求失败后,浏览器按顺序探测预设的备用地址,跳到第一个能通的;备用地址全部不可达,才显示离线页面。仅增强版和定制版可用。Critical sites can have HA rules attached. After a request to the primary fails, the browser probes the preset backup addresses in order and redirects to the first reachable one. The offline page appears only if none of the backups are reachable. Available in the Enhanced and Custom editions only.

高可用High availability增强版及以上Enhanced & up
04 · 授权版本Editions

三个授权版本,按规模和所需服务选择Three editions, chosen by scale and the services you need

全功能版已经开放全部 CDN 核心功能,价格按节点数和 Zone(根域名)配额分档。增强版在同样的核心之上加了高级功能和专家服务,定制版再加上定制研发与专项交付。The Full edition already includes every CDN core capability, priced by node count and Zone (root domain) quota tier. Enhanced keeps that same core and adds advanced capabilities and expert services. Custom goes further, with project-specific development and delivery.

全功能版Full 核心功能全部开放Core capabilities included
¥399/月 起/mo & up

10 个节点、100 个 Zone 起,共五档配额Starts at 10 nodes and 100 Zones, across five quota tiers

私有化运营一套 CDN 需要的核心能力,这一档都有。This edition has the core capabilities needed to run a private CDN.

站点接入、缓存与源站池Delivery, caching & origin pools 安全防护、证书与 DNSSecurity, certs & DNS 日志分析、节点运维与开发者接口Log analytics, node ops & developer API
节点数 / Zone 配额:以授权文件为准Node / Zone quota: set by license
定制版Custom 定制研发与交付Custom R&D
按需评估Scoped quote

定制研发与定价都按项目范围评估Development scope and pricing are both assessed per project

面向更大规模或特殊部署需求,按项目范围做定制研发。For larger scale or special deployment needs, with development scoped to the project.

包含增强版的高级功能与专家服务All the advanced capabilities and services from Enhanced 定制功能开发、专项交付与验收Custom feature development, project-specific delivery & acceptance 节点数、Zone 配额及能力组合按需定义Node / Zone quotas and capability mix defined as needed
节点数 / Zone 配额:按需定制Node / Zone quota: tailored

价格看两件事:授权节点数,和授权站点数。授权站点按根域名 Zone 算,同一个 Zone 下的子域名不额外占配额。增强版是所选全功能版基础月费再加 ¥999/月,定制版按需求范围评估。五档完整价格和计算器在授权定价页,版本之间的差异见 高级功能对比 Two numbers set the price: how many nodes you license, and how many sites. Licensed sites are counted per root-domain Zone, and subdomains under the same Zone use no extra quota. Enhanced is the Full base monthly fee you choose plus ¥999/mo, and Custom is priced against the scope of the project. All five price tiers and a calculator are on the pricing page, and the advanced comparison shows how the editions differ.

05 · 功能对比Feature comparison

核心功能三个版本都开放,
高级能力与服务按需增加
All three editions include the core; advanced capabilities and services are added as needed

下面是首页摘选的几行,完整的逐项矩阵在功能对比页。三个版本的核心功能状态一样,差别集中在高级功能、专家服务和定制研发上。These rows are a homepage selection; the full item-by-item matrix is on the feature comparison page. Core capabilities read the same across all three editions, and the differences sit in the advanced features, the expert services and the custom development.

FunCDN 三种授权版本对比(首页摘要,完整对比见功能对比页)FunCDN three-edition comparison (homepage highlights; see the full comparison page)
功能 / 服务Feature / service 全功能版Full核心功能全部开放Core capabilities included 增强版Enhanced高级能力与服务Advanced & services 定制版Custom定制研发与交付Custom R&D
CDN 核心功能(接入 · 缓存 · 安全 · 证书 · 日志分析 · 运维 · API)CDN core (delivery · cache · security · certs · log analytics · ops · API) 全部开放Included 全部开放Included 全部开放Included
节点 / Zone 配额(Zone = 根域名,子域名不额外占配额)Node / Zone quota (Zone = root domain; subdomains use no extra quota) 按所选档位Per chosen tier 按所选档位Per chosen tier 按方案Per plan
高级功能组合Advanced feature set 不含Not included 包含Included 包含Included
7×24 小时技术支持7×24 engineer support 不含Not included 包含Included 包含Included
页面级高可用Page-level high availability 不含Not included 包含Included 包含Included
部署评审与迁移协助Deployment review & migration assistance 不含Not included 包含Included 按方案Per plan
定制功能研发Custom feature development 不含Not included 不含Not included 按需评估Scoped
专项交付与验收Project-specific delivery & acceptance 标准交付Standard 增强交付Enhanced 定制里程碑Custom milestones

功能状态同时用符号和文字标注,不只靠颜色:✓ 表示全部开放或包含— 表示不包含。三个版本都开放全部核心功能,配额按所选档位或定制方案授权。增强版和定制版在此之上增加高级功能与专家服务,页面级高可用只是其中一项;定制版还包括定制研发与专项交付。 Status uses a symbol plus text, never color alone: ✓ included or enabled, — not included. All three editions have the full core, with quota licensed by the chosen tier or by a custom plan. Enhanced and Custom add advanced capabilities and expert services on top of that, and page-level HA is only one of them. Custom also covers project-specific development and delivery.

06 · FAQ

常见问题Frequently asked

这里列出三个常见问题。部署、授权、配额、高可用、日志分析和旧版本兼容的完整说明都在常见问题页。Three common questions. The full answers on deployment, licensing, quota, high availability, log analytics and legacy compatibility are on the FAQ page.

FunCDN 采用什么部署方式?What deployment model does FunCDN use?
私有化、自建。一套系统包含主控(API 服务与管理面板)、边缘节点、可选的回源中继,以及常驻在每台主机上的 cdn-agent。这些组件都原生运行在您自己的 Linux 服务器上,由主控统一编排。Private and self-hosted. A system is made up of the control plane (the API service and the web panel), edge nodes, an optional origin relay, and a cdn-agent resident on every host. All of them run natively on your own Linux servers, orchestrated by the control plane.
哪些版本支持高可用?能力边界是什么?Which editions support HA, and what's its scope?
页面级高可用只向增强版和定制版开放。全功能版能看到功能入口,但要用起来需要升级。它只对页面导航请求做容灾切换,并不是把站点的全部子资源都透明接管。查看高可用工作原理 →Page-level HA is available in Enhanced and Custom only. The Full edition shows the entry point but needs an upgrade before you can use it. Failover applies to page-navigation requests only; it does not transparently take over all of a site's sub-resources. See how HA works →
域名配额如何计算?How is the domain quota calculated?
按节点数和 Zone 数量算。一个 Zone 就是一个根域名,它底下的子域名都算进同一个 Zone,不额外占配额。实际的配额上限以授权文件为准。By node count and Zone count. One Zone is one root domain, and every subdomain under it belongs to that same Zone without using extra quota. The actual ceiling comes from your license file.

按需要选择授权版本和档位Choose the edition and tier you need

按节点数和授权站点数(以根域名 Zone 计)透明计费。选哪一档看实际部署规模,选哪个版本看您需要哪些高级功能与服务。Transparent pricing, based on licensed node count and licensed sites counted per root-domain Zone. The tier follows your deployment size; the edition follows which advanced capabilities and services you need.