Hybrid cloud network diagram template
A head office network joined to a cloud VPC by a site-to-site IPsec VPN. The office has a users segment and a server room; the VPC has a public subnet for Kubernetes and serverless functions and a private subnet for the managed database and object storage.
Use it to document how on-premises identity and servers reach cloud workloads, and which systems customers reach directly from the Internet.
How it's laid out
- The office (10.0.0.0/16) and the VPC (10.50.0.0/16) use non-overlapping ranges, which a VPN between them needs. Schema flags overlapping subnets if you change them.
- Customer traffic arrives at the cloud load balancer. Office traffic to cloud workloads goes through the VPN gateway.
- SaaS applications (mail, chat, ticketing) use single sign-on from the office directory.
Networks and segments
| Name | Kind | Subnet | VLAN | Notes |
|---|---|---|---|---|
| Head office | Zone | 10.0.0.0/16 | - | On-premises |
| Users | Segment | 10.0.10.0/24 | 10 | - |
| Server room | Segment | 10.0.20.0/24 | 20 | - |
| Cloud VPC | Zone | 10.50.0.0/16 | - | Public cloud region |
| Public subnet | Segment | 10.50.1.0/24 | - | - |
| Private subnet | Segment | 10.50.2.0/24 | - | - |
Device inventory
In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.
| Device | Type | Hostname | IP address | Role | Owner | Segment |
|---|---|---|---|---|---|---|
| Internet | Internet | - | - | - | - | - |
| HQ firewall | Firewall | fw-hq-01 | 10.0.0.1 | - | Network | Head office |
| Access switch | Switch | - | 10.0.10.2 | - | Network | Users |
| Staff devices | Laptop | - | - | End User Device | - | Users |
| Directory | Directory / IdP | dc-01 | 10.0.20.10 | Domain Controller | IT | Server room |
| Hypervisor | Hypervisor | hv-01 | 10.0.20.20 | Hypervisor | IT | Server room |
| VPN gateway | VPN | - | 10.50.0.5 | - | Network | Cloud VPC |
| Load balancer | Load Balancer | - | - | Load Balancer | Platform | Cloud VPC |
| Kubernetes | Kubernetes | - | 10.50.1.10 | - | Platform | Public subnet |
| Functions | Serverless | - | - | - | Platform | Public subnet |
| Managed DB | Database | - | 10.50.2.10 | Primary | Data team | Private subnet |
| Object storage | Storage | - | - | - | Data team | Private subnet |
| SaaS apps | SaaS | - | - | - | - | - |
Rules it checks
The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.
Perimeter & segmentation
Internet-facing systems sit behind a firewall, databases aren't exposed directly, and traffic between networks passes a firewall.
- Internet-connected servers must sit behind a firewall
- Databases must not connect directly to the Internet
- Storage must not connect directly to the Internet
- Servers reaching across a network boundary need a firewall in the path
- Databases reaching across a network boundary need a firewall in the path
- Workstations must not connect directly to databases
Documentation completeness
Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.
- Servers must have an IP address
- Servers must have an owner
- Servers must have a role
- Servers must record their OS
- Databases must have an IP address
- Databases must have an owner
- Firewalls must have an IP address
- Routers must have an IP address
Start from this template
Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.
Use this template freeOther templates
- Small office networkFirewall, a staff LAN, a server VLAN and isolated guest Wi-Fi - the classic single-site SMB layout.
- Three-tier web applicationDMZ, web, app and data tiers with addressed hosts, labelled flows and two firewall boundaries.
- Zero trust accessUsers reach private apps only through an identity-aware access proxy backed by SSO, device checks and a SIEM.
- Home labRouter, managed switch and three VLANs - home, lab and IoT - for documenting your own setup.