Diagram template
Sankey: upright solid ribbons
MaxFour possible noncrossing upright ribbon routes split two source openings into three destination openings. Vertical front-plane thickness shows each supplied amount; shallow constant extrusion adds material, and direct labels retain route amounts and derived endpoint totals.
Categories
Included in
Max
When to use it
Use for two ordered sources allocating one common quantity to three ordered uses, with source one feeding use one or two and source two feeding use two or three. Suits programme funding, campaign expenditure or staffing-hour allocation. Totals add only supplied transfers; omitted pairs assert no observed zero. Explicit zero transfers have no solid thickness and retain a dashed trace and direct zero. At least one supplied transfer must be positive. This is a two-column allocation, not a multi-stage conservation model or arbitrary crossing network. Extrusion depth and horizontal length encode no quantity.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Typography
- Material
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Value label
- Text
- Sources
- Exactly 2
- Destinations
- Exactly 3
- Edges
- 1 to 4, each with from, to, and value
Related templates
All chart templates
Architecture: system contextA C4 system context diagram, a "who uses it and what it depends on" slide, or an integration overview: one system, one to four actors that use it, and one to five external systems it calls or that call it, each link saying what it does.
Architecture: dependency graphThree to twelve components that call or depend on each other with no fixed tiers, such as a microservice call map, a service dependency graph, or data lineage between systems, with links labeled by protocol or what flows (gRPC, REST, events).
Architecture: environmentsOne system shown as two to four copies that are compared side by side: dev, staging, and production environments with promotion between them, region A, region B, and disaster recovery with replication, or blue and green stacks.
Architecture: event hubEvent flows through one broker, bus, or topic hub with one to five producers and one to five consumers, such as Kafka topics, Google Pub/Sub, SNS fanning out to SQS queues, EventBridge rules, or a webhook gateway delivering to several handlers; built for fan-in and fan-out.
Architecture: grouped panels left to rightTwo to fourteen components placed in two to five networks, clusters, subnets, or accounts, such as an AWS VPC with public and private subnets or a Kubernetes cluster with namespaces, optionally inside one region with users or third-party services outside.
Architecture: isometric floating layer plates stacked with a clear gapA layered system where components rely on specific components in the layer directly below: software layers from experience through services to data, an operating model from strategy through operations to delivery teams, or a data stack from reports through warehouse and pipelines to sources.