Show your data path. Auditable. Customer-facing.
SkyeFlow renders the upload and download pipeline as Mermaid diagrams with frame-, shard-, and provider-level annotation — the same diagrams that satisfy auditor requests, security questionnaires, and customer-education sessions.
The data path, drawn correctly.
Mermaid LR-graph topology
The full upload-to-scatter and read-to-reconstruct topology rendered as a left-to-right Mermaid graph. Source of truth for security questionnaires — no longer drawn from memory in PowerPoint.
Upload pipeline detail
Frame-by-frame view: chunking, DEK derivation, AES-256-GCM encrypt, RS(5,2)">Reed-Solomon RS(5,2) encode, per-shard provider routing, async scatter.
Download pipeline detail
Manifest fetch, parallel shard pull, RS-decode-on-client, AES-GCM-decrypt-on-client, plaintext stream. No server-side reassembly.
Frame / shard / provider annotation
Every node in the diagram is labelled with the cryptographic primitive, frame index, shard index, and target provider. The diagram reads like a runbook.
CSR variant
Customer-Specific Rendering: feed a customer's connexion set and policy, get a diagram showing how a sample file would flow through that specific configuration. Useful for private demos and procurement reviews.
Embeddable
Drop the diagram into a customer's own intranet, security wiki, or compliance documentation. The Mermaid source is portable; the rendered SVG is self-contained.
Why a visualisation product, separate from the platform
The SkyeConnex platform handles the actual work — encrypt, encode, scatter, reconstruct. SkyeFlow handles a distinct, equally important job: communicating that work to people whose decisions depend on understanding it. Auditors. CISOs. Procurement teams. Regulators. End customers in a sovereignty-sensitive vertical.
Most architecture diagrams in this space are produced once in PowerPoint, become inaccurate within a quarter, and persist as the canonical artefact for years. SkyeFlow inverts that: the diagram is generated from the live configuration. It is never out of date because it is never frozen.
What the upload diagram contains
The detailed upload pipeline renders every stage that touches the data:
- Client-side frame boundaries (~5 MB per frame, AES-256-GCM nonces deterministic from frame index).
- Per-file DEK derivation and UMK-wrap. The wrap mode (classical-only or PQ-hybrid) reflects the tier.
- Reed-Solomon RS(5,2) erasure-coding step, showing all seven output shards.
- Per-shard provider routing based on the geo-policy resolver. Each shard's target jurisdiction is labelled.
- Async scatter with idempotent upload keys. Retry boundaries are explicit.
What the download diagram contains
The download diagram emphasises client-side reconstruction:
- Manifest fetch — the shard topology and DEK for the requested file.
- Parallel pull of seven shards. Five-of-seven success threshold.
- Client-side Reed-Solomon decode. Server never assembles the file.
- Client-side AES-GCM decrypt frame by frame. Plaintext streams into the application as decoded.
Customer-specific rendering
The CSR variant generates a diagram tailored to a specific customer's configuration. Fed the customer's connexion set (the seven providers they use), the geo-policy (allow-list / block-list / strict-mode), and the tier (Free / Pro / Sovereign), SkyeFlow produces a diagram showing the exact data path that a sample upload would traverse. This is the artefact procurement teams actually want for their security review — not an abstract architectural overview, but the specific pipeline as configured for their account.
Show, don't tell.
Book a session. We'll generate a CSR diagram for a configuration that resembles yours — live, with your provider mix, your geo-policy, your tier.