What are you drawing?
Twenty live blueprints. Pick a use case, or scroll the lot.
Every blueprint
All 20, every one of them live
Basic enterprise Azure environmentAn on-premises estate extended into Azure over a private circuit, with identity, workloads and shared services in their own spokes around one inspection point.
Network topologies, physical and logicalThe same site drawn twice — the cabinets and the cabling, then the addressing and the routing — with a mermaid sequence for the failover.
Order to cash, across eleven systemsEvery system an order touches between the checkout and the ledger, and every hop between them carrying its transport, its retry rule and the team whose pager it wakes.
The order model, entity by entityTwelve entities, their keys and the events that change them: the operational schema, the star schema the warehouse reads, and a dictionary down to the column.
One platform, four hundred tenantsHow a single deployment serves four hundred customers without leaking between them: tenant routing, isolation the database enforces rather than the code, and what a migration costs four hundred times.
Sixty thousand devices, one measurement modelTime-series modelling at fleet scale: the cardinality budget, the tag that tripled the storage bill, two ingest paths for a good connection and a bad one, and ten years of history for less than a month of raw.
Datacentre exit, wave 3 in flightA migration programme mid-flight: the client's own draw.io estate annotated wave by wave, and a cutover runbook, an owner and a rollback point on every workload.
Multi-region failover, tested every quarterTwo AWS regions with recovery objectives on every service, and the evidence from the last real failover attached to the runbook steps it exercised.
Platform assessment before a funding roundAn advisory findings pack whose estate was drafted by AI from the client's own documentation, with a severity and a remediation pinned to every shape.
Client design pack, options and allEverything a consultancy hands over: the proposal, the options that lost and why, the risks, the cost, the whiteboard it came from and the handbook the client keeps.
Ship it — commit to productionOne service's whole delivery path: short branches, four gates that cannot be waived, Argo CD as the only way in, and the error budget that decides when to stop.
A webhook relay, explainedWhat a README wants to be: an architecture drawing whose every box opens on the component behind it, the state machine that defines the delivery guarantee, and the schema under it.
Multi-account AWS landing zoneThree accounts drawn from a live read-only scan. Open any subnet for its CIDR, its tags and what is running in it right now.
Azure hub-and-spoke, end to endA hub, four spokes, and the routing view that shows which peering actually carries traffic — not which one the wiki says does.
Network site topologyOne site from the edge router down to the access layer. Every device opens on its port map, its addressing and whether it is up right now.
Your first two weeksA folium for the reading and four podiums for the doing, so a new engineer has one link instead of a wiki page full of them.
Kubernetes platform referenceLong-form folium for the concepts, mermaid sequences for the control loops, and a Vellum topology you can click into.
Global WAN network diagramSites across four regions and the circuits between them — the excalidraw design from the workshop beside the topology that got built.
Zero-trust access reviewThe quarterly entitlement flow imported straight from draw.io, with the live ticket for each approval attached to its step.
Lakehouse, ingest to dashboardA podium tour of the pipeline, Continuum on the warehouse, and a stratum per hop carrying its freshness SLA.
Every card above opens on a canvas like this — not a screenshot of one.
Open the live blueprintIt loads here as you reach it.
Live —click any shape to see the magic