场景
上线前的网络评审：公网与 DNS、负载均衡、防火墙、VPC 与子网框架，以及它们保护的服务器或 Kubernetes 工作负载。
面向平台讨论的网络拓扑：边缘、负载均衡、子网及其背后的服务。与 C4、Kubernetes 同一编辑器，团队共用一种语言。网络包在 Free。
你画什么
网络架构图
- Internet 与 DNS
- 负载均衡、路由器与交换机
- Firewall
- 作为框架的 VPC 与 subnet
- Server、rack、wireless、CDN
- 给评审听众的 Legend
为什么选 Archboard
Archboard 是网络拓扑画布，与 Kubernetes、C4 同在一个托管工作区。端口与正交连线让路径可见。在 Free 上绘制网络包；评审走出平台团队时订阅 Pro 以获得无限节点与嵌入。
此画布上的节点包
网络 · 云 · 安全 · Kubernetes
所有内置节点包都在 Free 中（3 张图，每张 15 个图表节点 + 150 个便签、文本、贴纸和思维导图主题，带品牌的公开分享，与您的 AI 智能体实时编辑）。Pro 增加无限图表与节点、让队友实时编辑的席位、嵌入和无水印导出（$10/席/月）。
一次会话怎么走
用 Google 或 GitHub 登录后打开画布
放置 Internet → DNS → 负载均衡 → 防火墙 → VPC/subnet
在子网框架内放下服务器或 Kubernetes 节点
分享带品牌的公开查看链接，或为变更单导出 SVG/PNG
Network diagrams people can point at
Network architecture diagrams usually fail at the pointer test: in a review, nobody can point at the path a packet takes. Icons float without frames, subnets are implied, and the firewall might as well be decorative. A network topology canvas passes the test by making the path visible, from the Internet to DNS to load balancer to firewall to VPC and subnet frames, with servers or Kubernetes workloads inside them. Orthogonal edges carry the hops cleanly; labeled edges carry the policy, like which port the firewall allows. When the whole path is on one board, the review moves from guessing to deciding.
Frame aggressively. VPC and subnet frames turn a pile of servers into an address plan reviewers can read: public subnets hold the load balancer, private subnets hold the workloads, and the firewall sits visibly between the edge and everything else. Add a legend for the review audience, because reviewers who do not live in the network still need to read it. Put DNS early in the path; half of all network mysteries start with name resolution, and the diagram should say so.
From topology sketch to change ticket
A network diagram becomes operational when it attaches to the change process. Export an SVG or PNG for the ticket, share a branded public link for the pre-launch review, and snapshot a revision before the firewall rule changes, since the before-shape is the fastest way to roll a conversation back. Keep the Kubernetes workloads that sit behind the firewall on the same canvas instead of a separate drawing; the subnet frame should contain what it actually routes to, whether that is servers or Pods. Tickets with a live link get approved faster than tickets with a stale screenshot.
The Network pack ships on Free with Cloud, Security, and Kubernetes packs beside it, because topologies never stop at the subnet edge. Combine Internet, router, switch, and CDN nodes with the firewall and VPC frames, and let the canvas hold the whole story from edge to workload. Pro adds embed plus watermark-free snapshots for the tickets that leave the platform team. Draw the path the packet takes, and then point at it.
Open a published example
- Datacenter NetworkInternet, DNS, load balancer, firewall, VPC, and subnet servers in path order.
- Zero Trust PerimeterIdP, WAF, firewall, vault, and certificates layered around workloads.
Questions
What should a network diagram always show?
The full packet path: Internet, DNS, load balancer, firewall, VPC and subnet frames, and the servers or workloads inside them, along with labeled edges for policy like allowed ports and protocols.
Can servers and Kubernetes share one topology?
Yes. Drop servers or Kubernetes nodes inside the same subnet frames on one canvas. Reviewers see what the subnet routes to without reconciling two drawings.
How do I present this to non-network reviewers?
Add a legend, keep one packet path per board, and share the live link so reviewers can pan and zoom. Export SVG or PNG when the change ticket needs a frozen snapshot.