Building Blueprintr!
A 100G leaf-and-spine fabric drawn twice: the physical pods, spines and border once, then the EVPN/VXLAN overlay of tenants, VRFs and VNIs that rides on it. Every switch opens on its interfaces, addressing and operating…
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
Four slides on what a folium is, how its page tree works, and where everything else is configured.
A five-slide walkthrough of the authoring loop, from the rail to a stratum.
Ownership, visibility and filing are decided separately — and only one of them changes the URL.
Your directory pushes to the SSO service; Blueprintr pulls from it. And the one direction SCIM will not reverse.
Why a personal key and an organisation key are not one credential with different permissions.
Import copies content in once and it becomes yours; a connector leaves it where it is and renders it live per viewer.
Open, then approved and merged, rejected, or withdrawn — and why the docs agent files one rather than writing the page.
A refresh rewrites the Continuum-managed half of a canvas and never touches the shapes you drew.
SSO decides who may sign in; SCIM decides who is a member. Without SCIM a leaver keeps the membership and the seat.
A stratum is bound to exactly one shape, and can be linked to from anywhere.
What belongs at the organisation level and what belongs to a team.
Draft, published version, and the next draft — what readers see while you edit.
What decides who can read a blueprint or folium: status first, then visibility, capped by organisation policy.
Vellum draws a diagram, a blueprint wraps it with strata, files and prose, and one publish makes it readable four ways.
One shape on a diagram surface, bound to a stratum holding five tab kinds.
What a fleet of connected heat pumps sends and where it lands: the device registry, an ingest path for a good connection and one for a bad one, the measurement schema and its cardinality budget, and how ten years of hist…
How one deployment serves four hundred customers without leaking between them: the control plane and the two data planes, tenant routing, isolation the database enforces rather than the code, per-tenant fairness, and wha…
The same retailer modelled from the inside: twelve operational entities with their keys and constraints, the events that move an order between them, the star schema the warehouse reads, and a dictionary down to the colum…
Every system an order passes through between the checkout and the ledger, and every hop between them: its transport, its schedule, its retry rule, its owning team, and what happens to the order when that hop is down.
An advisory engagement's findings pack. The client's estate was drafted by AI from their own documentation and corrected by hand, and all sixteen findings are pinned to the shape each one concerns with a severity and a r…
Two AWS regions with recovery objectives on every service, a twelve-step failover runbook drawn as a diagram, and the evidence from the last real failover attached to the steps it exercised. The runbook and the drawing a…
A migration programme mid-flight: the client's own draw.io estate annotated wave by wave, the landing zone the workloads land in, a cutover runbook and a rollback point on every workload, and the steering pack it was all…
What a project README wants to be and cannot: one architecture drawing whose every box opens on the component behind it, the state machine that defines the delivery guarantee, the schema that implements it, the docs, and…
The whole delivery path for a service: trunk-based branches, the four gates that cannot be waived, a signed supply chain, Argo CD as the only deploy path, progressive rollout across two regions, and the error budget that…
The whole artefact a consultancy hands a client: the proposed design, the options that were rejected and why, the risks, what it costs, the whiteboard it came from, the deck it was presented with, and the handbook the cl…
Meridian's analytics estate from Track event to executive dashboard: three feeds into a bronze/silver/gold lake, nightly models, Redshift and Athena — with a podium tour, a live Continuum warehouse scan, and a freshness-…
Meridian's quarterly entitlement review: the draw.io flow the team actually runs, each step carrying its live ServiceNow ticket, the access topology it polices, and the controls and evidence that prove it happened.
Meridian's seven-site WAN across EMEA, AMER, APAC and the Middle East: the original Excalidraw workshop design beside the Vellum topology that was built, with every circuit, route preference and failover obligation docum…
The reference for track-prod, Meridian's EKS platform: a clickable Vellum topology with strata across the estate, mermaid sequences for the control loops, the platform handbook as a long-form folium, and the add-on estat…
Meridian's new-engineer onboarding in one link: a two-week journey map with a stratum on every milestone, the engineering handbook as a folium, and four podium decks — dev environment, first deploy, reading a blueprint,…
Rotterdam HQ from WAN hand-off to desk port: redundant perimeter, core, distribution and access layers, with a real port map and addressing record behind every device and live Continuum Link tabs beside the authored oper…
Meridian's corporate Azure estate: a firewalled hub and four peered spokes reached over ExpressRoute from Rotterdam. The Continuum tab carries a scanned hub-and-spoke environment whose Routing view shows which peering ac…
Meridian's three scanned AWS accounts — network, production and non-production — behind one transit gateway, with centralised inspection and egress and every subnet documented down to CIDR, tags and running workloads.
Basic Enterprise Azure Environment
Typical architecture for vWAN with AFW - this is a test
A placeholder article for the Blueprintr Docs knowledge base.