Infrastructure diagrams, drawn in layers
Server diagrams tend to multiply: a rack elevation, a network map, a virtualization layout, a service flow — the same box drawn in four documents that drift apart the moment one changes. Archyscape keeps them on one canvas as stacked layers.
Same place, different layer
Space, equipment, virtualization and services each get a layer, and every layer shares the same coordinates. A service card sits right above the VM it runs on, and the VM right above its host.
Between layers you draw relationships — runs on, located in, uses — so when something below stops, you can see what stops with it above.
How it works
- Drag routers, switches, servers, racks, VMs and services from the palette. Drop them inside a zone or rack and they belong to it.
- Connect things on the same layer (network, power, storage, data) with the connect tool (C); link layers from the side panel.
- Open the exploded view to fan the layers out, pick an element and run impact analysis to highlight everything affected above and below.
- Record a scenario and play back a request as a dot travelling user → switch → server → VM → service.
- Export PNG (paste into slides), SVG, a self-contained HTML viewer, Markdown or an AI-ready summary — optionally with IPs masked.
Your files stay on your computer
No account, no server. A document is one .archyscape (JSON) file: in Chrome and Edge it saves back to the file you opened, elsewhere it downloads. Nothing you draw is sent anywhere — diagrams are full of IPs and asset details, so that came first. Visits are counted only with cookie-free Cloudflare Web Analytics.
Unsaved changes are kept as a recovery copy in this browser, so closing the tab by accident isn't the end.
Web and desktop
Drawing, analysis, flow playback and export all work on the web. The Windows desktop app (coming to the Microsoft Store) adds opening SSH, RDP and VNC straight from a card, splitting a rack into its own linked file, and reloading files an agent has edited.
Start from an example
- Three-tier web service diagramThe classic split — web servers in the DMZ, application and database servers inside — drawn as an equipment layer with the services stacked on top.
- Disaster recovery (DR) pair diagramA primary site and a DR site side by side, with storage replication, database log shipping and the GSLB failover on one canvas.
- 42U rack elevationOne rack with ToR switches, a firewall, a management switch, DB and app servers, storage and a UPS — each placed at its U position.
- Network separation diagramA business network and an internet network kept apart: the internet only through VDI, files only through a cross-domain transfer server.