High-Level Design Template
Draw the system's main parts and how they connect, and keep each design decision and its reasoning one click behind the part it shapes.
Free forever on the Personal plan
High-level designs: an example
Parts by role
Components named for what they do, not for their SKU or address.
Decisions with reasons
Each choice records the options weighed and why one was chosen.
A path to the LLD
Each part links to the low-level design that details it.
The basics
What is a high-level design?
A high-level design (HLD) describes the architecture of a system or platform at the level of its main components and how they connect: sites, networks, platforms and workloads, the key design decisions and the requirements they meet. It is detailed enough to agree the approach, and leaves addresses, sizes and configuration to the low-level design.
HLDs are reviewed by design authorities, clients and security teams, and they set the boundaries everyone builds within. A good one makes its decisions explicit, so reviewers debate the decision rather than the drawing.
In Blueprintr the diagram is the spine of the HLD: each part opens a stratum with its decisions and reasoning, and links down to the low-level design that details it.
Why Blueprintr
High-level designs that survive review
The architecture on one diagram, the reasoning behind each part.
Icons for every platform
Draw with the Azure, AWS, Microsoft, Kubernetes and network icon sets, or your own SVGs, and nest regions, hubs, spokes and sites as containers.
VellumDecisions behind each part
Give every part a stratum with the decision it embodies, the options weighed and the reason, in a table reviewers can scan.
StratumStart from what exists
On the Team plan, Continuum Cloud draws the AWS and Azure resources a client already has from a read-only scan, as a starting point for the design.
ContinuumLinked to the low-level designs
Link each part's stratum to its low-level design blueprint, so reviewers can follow the design down a level and back.
Approved before it changes
On team-owned blueprints, require the design authority's approval before an edit is merged into the published HLD.
Every version kept
Each publish keeps a snapshot. On the Team plan you can compare the text of two versions and restore one.
Blueprints
How to
How to write a high-level design in Blueprintr
Create a blueprint
Sign up free and create a blueprint, or start from the Azure hub-and-spoke landing zone template in the Compendium.
Draw the main parts
Add the sites, networks, platforms and workloads as containers and icons, named by role.
Record the decisions
Add a stratum to each part with the decision, the options weighed and the reason.
Link the detail
Link each part to its low-level design once it exists.
Review and approve
Share the HLD with the design authority and publish the approved version.
Start from a template
Azure hub-and-spoke landing zone
A hub VNet with gateway, Azure Firewall, Bastion and shared services, peered to workload, identity and data spokes, with strata for address plans and firewall policy.
FAQ
Questions about high-level designs
Is this high-level design template free?
Yes. The Vellum editor, the icon packs, strata and the Compendium's templates are available on the free Personal plan. Approval workflows and version comparison are part of the Team plan.
What should a high-level design include?
Scope, the main components and how they connect, sites and network paths, the key decisions with the options weighed, security boundaries, resilience and recovery targets, and links to the low-level designs.
What is the difference between a high-level design and a low-level design?
The HLD agrees the architecture: which parts exist, how they connect and why. The low-level design specifies how each part is built: addresses, sizes, names, rules and settings, ready for an engineer to implement.
Can Blueprintr draw an HLD from my existing cloud?
On the Team plan, Continuum Cloud draws the AWS and Azure resources it finds with read-only access. Use that as a starting point, then add the target state and the design decisions yourself.
Who approves a high-level design?
Usually a design authority or architecture board, with the client's sponsor. On team-owned blueprints, Blueprintr records each approver's sign-off before the change is merged and published.
Can I export the HLD as a document?
You can export the diagram as PDF, PNG or SVG, and the blueprint as a zip with every stratum as markdown. There is no Word export.