Building Blueprintr!
Meridian's two 24U comms room racks, unit by unit, with a record behind every unit. Click any unit for its serial, power, uplinks and owner, or open the Cabling tab for the patch schedule: every port, its VLAN and what i…
A retailer's blameless postmortem for a 44-minute card payments outage: the timeline by phase, the impact, why it happened and the actions with owners, then the full written review. Click any box for the detail behind it…
API documentation drawn around the API itself: how to get a token, the endpoints by resource with their methods colour coded, and the webhooks sent back. Click any endpoint for its reference and code examples, or open th…
An onboarding guide for a new engineer: five milestones over ten working days, two tasks under each, and the people to meet, with the deck for the first morning. Click any task for how to do it, or open the day one deck.
Kestrel Outdoor's service desk guide for a store till that cannot take card payments, from the first question to a fix or an escalation. Click any check for how to run it, the commands the desk runs and the evidence to r…
A retailer's returns process as a swimlane map: customer, store, warehouse and finance lanes, for returns in store and by post. Click any step for its owner and rule; the warehouse inspection opens its own sub-process, a…
A retailer's standard operating procedure for opening a store: what to have ready, six numbered steps, one readiness check and where to go when it fails, plus the written SOP on the Procedure tab. Click any step for its…
Technical documentation for an order service, built around its diagram: callers, internals, dependencies, consumers and the documentation set, with config and schema on the parts and the system as Mermaid on the As code…
An IT knowledge base drawn as a map of the services it covers, with the most asked-for article under each one, and the articles published as a Folium help site. Click any article tile to read it, or open the Knowledge ba…
An architecture decision record as a decision map: the drivers, three options, the decision and its consequences for a retailer's integration platform. Click any tile for its reasoning, the decision for its objections, o…
A STRIDE threat model of an online ordering platform as a data-flow diagram: trust boundaries, numbered flows and six threats pinned to the elements they target, with the register in its own tab. Click a threat for its s…
A consultancy's plan for moving a food retailer to Azure in five waves, each system coloured by its strategy. Click any system for its approach, the file, WMS and ERP cards for a cutover runbook, or the Dependencies tab…
A food retailer's estate today, the four streams of work that close the gap, and the target estate on Azure, row by row, with the business case in its own tab. Click any system or stream for its risk, owner and plan.
A consultancy's low-level design for an ERP workload in Azure: subnets, addresses, VM names and zones, the database, private endpoints, routes and rules. Click any resource for its exact settings; the main six also show…
A consultancy's high-level design for a food retailer's Azure platform: sites over SD-WAN, a hub with the firewall, one spoke per workload and recovery in a second region. Click any part for its role; six key parts open…
A consultancy's one-page overview of a food retailer's target architecture: channels, applications, integration and data on a shared platform, with the board pack that presents it. Click any layer or system for its owner…
A consultancy's solution design for a retailer's online ordering platform: users, new services, changed systems and the document's sections, with the full design document in its own tab. Click any tile for its section, o…
An MSP handing a manufacturer's IT to its new in-house IT manager: access, contracts, documentation and knowledge transfer, each item coloured by status, with the covering letter and the evidence behind each item. Click…
An MSP's quarterly business review: the dashboard, the written report and the meeting deck, from one set of figures. Click any tile for the numbers behind it, or open the report and the deck.
An MSP's plan for replacing a law firm's core switch in a Sunday window: who does what and when, the 20:00 go or no-go decision and the rollback, with the change record and the exact commands. Click a step for its instru…
An MSP's runbook for a dental practice that drops off the network, in four phases: detect, triage, mitigate, recover. Click any step or phase for its procedure; four steps add a Commands tab with the bash or PowerShell t…
An MSP's survey of a new veterinary clinic, drawn as a floor plan: proposed access points, data points per room and measured cable runs, with the comms cabinet drawn unit by unit on its own tab. Click a room for the surv…
An MSP's assessment of a manufacturer's office and factory network, with numbered findings pinned to the devices they affect and coloured by risk, and the written report. Click a finding for its evidence and fix, or open…
An MSP's six-week plan for taking on a veterinary group, as a swimlane: account management, projects, the NOC and the client, week by week, and the deck that walks the client through it at kickoff. Click any step for its…
An MSP's documentation for a two-office law firm: the Microsoft 365 tenant, cloud apps, both offices and the services the MSP runs. Click any tile for its owner, contract and what to do when it fails, or open the client…
Meridian's plan for losing Track & Trace's primary AWS region: what is copied where, how DNS fails over and five timed steps. Click a step for its commands and owner, or open the board briefing, a five-slide Podium deck…
Meridian's firewall zones coloured by trust, each on its own interface of the PA-3410 pair: internet, guest, remote staff, staff, servers, cloud and management. Click a zone for what it may reach, and its Policy tab for…
Meridian Track's services, queues, data stores and outside providers, coloured by criticality. Click any tile for its owner, what it calls, what calls it, its SLO and what fails with it.
Meridian's production EKS cluster: ingress, the team-track namespace and its workloads, add-ons and node pools. Click an object for its settings and manifest, or open the Deploy tab for one release from merge to rolling…
Meridian's colocation cage drawn from above: rack rows around a contained cold aisle, the meet-me room and the A and B feeds. Click a rack for its contents and elevation, or open the Power tab for the chain from the grid…
Meridian's AWS production account and Azure subscription, joined at the AMS3 edge: VPCs, transit gateway, inspection, the workload, hub and spoke. Click any resource for its ranges, routing and owner.
Meridian's network from the Rotterdam HQ access layer to the AMS3 colocation edge, with internet, Direct Connect and ExpressRoute links. Click any device or site for its addressing, links, owner and failure plan.
Seven habits for working in Blueprintr, all on the free plan: import, tabs, strata, visibility, embeds, templates and keyboard shortcuts. Click a numbered box for the detail.
Meridian's seven-site WAN across four regions. The workshop drawing and deployed topology sit alongside circuit records, routing policy and failover procedures.
Arbor's proposed managed platform for Brightwater Foods. Includes design options, costs, risks, the workshop drawing and the service handbook.
Meridian's quarterly entitlement review. Includes the approval flow, access topology, ServiceNow records, escalation dates and evidence requirements.
Meridian's Azure hub and four spokes, connected to Rotterdam through ExpressRoute. Includes routing, identity, corporate workloads and operations notes.
The Rotterdam HQ network from WAN hand-off to access switches, with port maps, addressing records and device operating notes.
A 100G leaf-and-spine fabric with physical and EVPN/VXLAN views. Includes switch interfaces, tenant addressing, routing and maintenance procedures.
An Azure hub-and-spoke design connected to an on-premises network through ExpressRoute. Includes identity services, application workloads, addressing and firewall policy.
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.
Thornhill's telemetry pipeline for 60,000 heat pumps. Covers ingestion, measurement schemas, tag cardinality, retention and rollups.
Sandgate's platform for 400 tenants. Covers routing, row-level security, pooled and siloed databases, resource limits and schema migrations.
Kestrel Outdoor's operational schema, order events and warehouse model, with keys, constraints and a column-level data dictionary.
Kestrel Outdoor's eleven order-processing systems. The interface register records each connection's transport, schedule, retries, owner and failure handling.
Windlass's platform review before its Series C round. Sixteen findings are linked to the affected components, with severity, supporting evidence and remediation plans.
Quayside's two-region AWS design and twelve-step failover procedure, with recovery targets, failback instructions and quarterly test results.
Halverstone's migration plan during wave 3. Includes the current estate, target landing zone, cutover procedures, rollback criteria and programme reports.
Rivulet's architecture, delivery state machine and database schema, with installation instructions, operating notes and a short walkthrough.
A service's delivery process from pull request to production. Covers CI checks, signed images, Argo CD, staged rollout, rollback and error-budget limits.
Meridian's event and partner feeds through bronze, silver and gold storage to Redshift, Athena and dashboards. Includes freshness targets, data contracts and replay procedures.
Meridian's track-prod EKS cluster. Includes topology, control-loop sequences, the platform handbook, operating procedures and add-on versions.
Meridian's two-week onboarding plan, engineering handbook and four walkthroughs covering local setup, deployment, blueprints and on-call work.
Meridian's network, production and non-production AWS accounts, joined through a transit gateway with shared inspection and egress. Includes subnet records and account controls.
Typical architecture for vWAN with AFW - this is a test
A placeholder article for the Blueprintr Docs knowledge base.